The patch titled viafb: pass reference to pci device when calling framebuffer_alloc() has been removed from the -mm tree. Its filename was viafb-pass-reference-to-pci-device-when-calling-framebuffer_alloc.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: viafb: pass reference to pci device when calling framebuffer_alloc() From: Harald Welte <laforge@xxxxxxxxxxxx> Signed-off-by: Harald Welte <HaraldWelte@xxxxxxxxxxx> Signed-off-by: Florian Tobias Schandinat <FlorianSchandinat@xxxxxx> Cc: Scott Fang <ScottFang@xxxxxxxxxxxxxx> Cc: Joseph Chan <JosephChan@xxxxxxxxxx> Cc: Jonathan Corbet <corbet@xxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/video/via/viafbdev.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff -puN drivers/video/via/viafbdev.c~viafb-pass-reference-to-pci-device-when-calling-framebuffer_alloc drivers/video/via/viafbdev.c --- a/drivers/video/via/viafbdev.c~viafb-pass-reference-to-pci-device-when-calling-framebuffer_alloc +++ a/drivers/video/via/viafbdev.c @@ -1857,7 +1857,8 @@ static int __devinit via_pci_probe(struc * variables */ viafbinfo = framebuffer_alloc(viafb_par_length + - ALIGN(sizeof(struct viafb_shared), BITS_PER_LONG/8), NULL); + ALIGN(sizeof(struct viafb_shared), BITS_PER_LONG/8), + &pdev->dev); if (!viafbinfo) { printk(KERN_ERR"Could not allocate memory for viafb_info.\n"); return -ENODEV; @@ -1982,7 +1983,7 @@ static int __devinit via_pci_probe(struc default_var.vsync_len = 4; if (viafb_dual_fb) { - viafbinfo1 = framebuffer_alloc(viafb_par_length, NULL); + viafbinfo1 = framebuffer_alloc(viafb_par_length, &pdev->dev); if (!viafbinfo1) { printk(KERN_ERR "allocate the second framebuffer struct error\n"); _ Patches currently in -mm which might be from laforge@xxxxxxxxxxxx are origin.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