The patch titled correct name for rtc-m41t80 has been added to the -mm tree. Its filename is correct-name-for-rtc-m41t80.patch *** 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 ------------------------------------------------------ Subject: correct name for rtc-m41t80 From: David Brownell <david-b@xxxxxxxxxxx> The new rtc-m41t80 driver name doesn't match its module name, which prevents it from properly hotplugging. Since it's new, no platforms yet depend on that name ... so this patch fixes the driver name to match its module name, rather than going the other way around with a MODULE_ALIAS(). NOTE: This sort of bug is a new thing to watch out for with new-style I2C drivers; previously I2C couldn't hotplug. Signed-off-by: David Brownell <dbrownell@xxxxxxxxxxxxxxxxxxxxx> Cc: Atsushi Nemoto <anemo@xxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/rtc/rtc-m41t80.c | 2 +- 1 files changed, 1 insertion(+), 1 deletion(-) diff -puN drivers/rtc/rtc-m41t80.c~correct-name-for-rtc-m41t80 drivers/rtc/rtc-m41t80.c --- a/drivers/rtc/rtc-m41t80.c~correct-name-for-rtc-m41t80 +++ a/drivers/rtc/rtc-m41t80.c @@ -892,7 +892,7 @@ static int m41t80_remove(struct i2c_clie static struct i2c_driver m41t80_driver = { .driver = { - .name = "m41t80", + .name = "rtc-m41t80", }, .probe = m41t80_probe, .remove = m41t80_remove, _ Patches currently in -mm which might be from david-b@xxxxxxxxxxx are origin.patch correct-name-for-rtc-m41t80.patch git-mmc.patch git-mtd.patch dma_free_coherent-needs-irqs-enabled-sigh.patch drivers-pmc-msp71xx-gpio-char-driver.patch driver-for-the-atmel-on-chip-ssc-on-at32ap-and-at91.patch clean-up-duplicate-includes-in-drivers-spi.patch rtc-periodic-irq-fix.patch rtc_irq_set_freq-requires-power-of-two-and-associated-kerneldoc.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