The patch titled fsl-diu-fb-update-freescale-diu-driver-to-use-page_alloc_exact-update has been added to the -mm tree. Its filename is fsl-diu-fb-update-freescale-diu-driver-to-use-page_alloc_exact-update.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: fsl-diu-fb-update-freescale-diu-driver-to-use-page_alloc_exact-update From: Timur Tabi <timur@xxxxxxxxxxxxx> Fix printk format specifiers, per Andrew Morton. Signed-off-by: Timur Tabi <timur@xxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/video/fsl-diu-fb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN drivers/video/fsl-diu-fb.c~fsl-diu-fb-update-freescale-diu-driver-to-use-page_alloc_exact-update drivers/video/fsl-diu-fb.c --- a/drivers/video/fsl-diu-fb.c~fsl-diu-fb-update-freescale-diu-driver-to-use-page_alloc_exact-update +++ a/drivers/video/fsl-diu-fb.c @@ -295,7 +295,7 @@ static void *fsl_diu_alloc(size_t size, virt = alloc_pages_exact(size, GFP_DMA | __GFP_ZERO); if (virt) { *phys = virt_to_phys(virt); - pr_debug("virt=%p, phys=%llx\n", virt, + pr_debug("virt=%p phys=%llx\n", virt, (unsigned long long)*phys); } _ Patches currently in -mm which might be from timur@xxxxxxxxxxxxx are origin.patch mm-add-alloc_pages_exact-and-free_pages_exact.patch fsl-diu-fb-update-freescale-diu-driver-to-use-page_alloc_exact.patch fsl-diu-fb-update-freescale-diu-driver-to-use-page_alloc_exact-update.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html