The patch titled
Subject: drivers/rtc/rtc-isl12022.c: Remove rtc8564 from isl12022_id
has been added to the -mm tree. Its filename is
drivers-rtc-rtc-isl12022c-remove-rtc8564-from-isl12022_id.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 ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Axel Lin <axel.lin@xxxxxxxxxx>
Subject: drivers/rtc/rtc-isl12022.c: Remove rtc8564 from isl12022_id
rtc8564 appears in i2c_device_id table of both rtc-isl12022.c and
rtc-pcf8563.c. commit 8ea9212c "rtc-pcf8563: add chip id" adds rtc8564
chip entry to pcf8563. isl12022 driver is modified from pcf8563 driver,
so this looks like a copy-paste bug.
Signed-off-by: Axel Lin <axel.lin@xxxxxxxxxx>
Cc: Roman Fietze <roman.fietze@xxxxxxxxxxxxx>
Cc: Jon Smirl <jonsmirl@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/rtc/rtc-isl12022.c | 1 -
1 file changed, 1 deletion(-)
diff -puN drivers/rtc/rtc-isl12022.c~drivers-rtc-rtc-isl12022c-remove-rtc8564-from-isl12022_id drivers/rtc/rtc-isl12022.c
--- a/drivers/rtc/rtc-isl12022.c~drivers-rtc-rtc-isl12022c-remove-rtc8564-from-isl12022_id
+++ a/drivers/rtc/rtc-isl12022.c
@@ -280,7 +280,6 @@ static int isl12022_remove(struct i2c_cl
static const struct i2c_device_id isl12022_id[] = {
{ "isl12022", 0 },
- { "rtc8564", 0 },
{ }
};
MODULE_DEVICE_TABLE(i2c, isl12022_id);
_
Patches currently in -mm which might be from axel.lin@xxxxxxxxxx are
linux-next.patch
drivers-rtc-rtc-max6902c-use-register-defines-instead-of-magic-numbers.patch
drivers-rtc-rtc-isl12022c-remove-rtc8564-from-isl12022_id.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
