[PATCH] mm/sparse.c: change printk()s to pr_*() notation
From: H Hartley Sweeten
Date: Tue May 19 2009 - 13:40:05 EST
Change all the printk()s in mm/sparse.c to the pr_*() notation.
Signed-off-by: H Hartley Sweeten <hsweeten@xxxxxxxxxxxxxxxxxxx>
---
diff --git a/mm/sparse.c b/mm/sparse.c
index da432d9..895cba9 100644
--- a/mm/sparse.c
+++ b/mm/sparse.c
@@ -308,9 +308,8 @@ static void __init check_usemap_section_nr(int nid, unsigned long *usemap)
usemap_nid = sparse_early_nid(__nr_to_section(usemap_snr));
if (usemap_nid != nid) {
- printk(KERN_INFO
- "node %d must be removed before remove section %ld\n",
- nid, usemap_snr);
+ pr_info("node %d must be removed before remove section %ld\n",
+ nid, usemap_snr);
return;
}
/*
@@ -319,10 +318,9 @@ static void __init check_usemap_section_nr(int nid, unsigned long *usemap)
* gather other removable sections for dynamic partitioning.
* Just notify un-removable section's number here.
*/
- printk(KERN_INFO "Section %ld and %ld (node %d)", usemap_snr,
- pgdat_snr, nid);
- printk(KERN_CONT
- " have a circular dependency on usemap and pgdat allocations\n");
+ pr_info("Section %ld and %ld (node %d)", usemap_snr,
+ pgdat_snr, nid);
+ pr_cont(" have a circular dependency on usemap and pgdat allocations\n");
}
#else
static unsigned long * __init
@@ -355,7 +353,7 @@ static unsigned long *__init sparse_early_usemap_alloc(unsigned long pnum)
/* Stupid: suppress gcc warning for SPARSEMEM && !NUMA */
nid = 0;
- printk(KERN_WARNING "%s: allocation failed\n", __func__);
+ pr_warning("%s: allocation failed\n", __func__);
return NULL;
}
@@ -384,8 +382,8 @@ static struct page __init *sparse_early_mem_map_alloc(unsigned long pnum)
if (map)
return map;
- printk(KERN_ERR "%s: sparsemem memory map backing failed "
- "some memory will not be available.\n", __func__);
+ pr_err("%s: sparsemem memory map backing failed "
+ "some memory will not be available.\n", __func__);
ms->section_mem_map = 0;
return NULL;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/