The patch titled driver-for-the-atmel-on-chip-rtc-on-at32ap700x-devices fix 2 has been removed from the -mm tree. Its filename was driver-for-the-atmel-on-chip-rtc-on-at32ap700x-devices-fix-2.patch This patch was dropped because it was folded into driver-for-the-atmel-on-chip-rtc-on-at32ap700x-devices.patch ------------------------------------------------------ Subject: driver-for-the-atmel-on-chip-rtc-on-at32ap700x-devices fix 2 From: Hans-Christian Egtvedt <hcegtvedt@xxxxxxxxx> rtc-at32ap700x driver updated to 2.6.22-rc4-mm2 kernel Signed-off-by: Hans-Christian Egtvedt <hcegtvedt@xxxxxxxxx> Acked-by: Alessandro Zummo <a.zummo@xxxxxxxxxxxx> Cc: David Brownell <david-b@xxxxxxxxxxx> Cc: Haavard Skinnemoen <hskinnemoen@xxxxxxxxx> Cc: Hans-Christian Egtvedt <hcegtvedt@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/rtc/rtc-at32ap700x.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN drivers/rtc/rtc-at32ap700x.c~driver-for-the-atmel-on-chip-rtc-on-at32ap700x-devices-fix-2 drivers/rtc/rtc-at32ap700x.c --- a/drivers/rtc/rtc-at32ap700x.c~driver-for-the-atmel-on-chip-rtc-on-at32ap700x-devices-fix-2 +++ a/drivers/rtc/rtc-at32ap700x.c @@ -202,7 +202,7 @@ static irqreturn_t at32_rtc_interrupt(in & ~RTC_BIT(CTRL_TOPEN)); rtc_writel(rtc, VAL, rtc->alarm_time); events = RTC_AF | RTC_IRQF; - rtc_update_irq(&rtc->rtc->class_dev, 1, events); + rtc_update_irq(rtc->rtc, 1, events); ret = IRQ_HANDLED; } _ Patches currently in -mm which might be from hcegtvedt@xxxxxxxxx are git-avr32.patch git-input.patch git-watchdog.patch rtc-make-example-code-jump-to-done-instead-of-return-when-ioctl-not-supported.patch rtc-dev-return-enotty-in-ioctl-if-irq_set_freq-is-not-implemented-by-driver.patch driver-for-the-atmel-on-chip-rtc-on-at32ap700x-devices.patch driver-for-the-atmel-on-chip-rtc-on-at32ap700x-devices-fix-2.patch driver-for-the-atmel-on-chip-rtc-on-at32ap700x-devices-fix-3.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