diff for duplicates of <20150728173058.GB2284@x1> diff --git a/a/1.txt b/N1/1.txt index e422d4a..06e25d5 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -2,87 +2,95 @@ On Tue, 28 Jul 2015, Dmitry Torokhov wrote: > On Tue, Jul 28, 2015 at 09:40:19AM +0100, Lee Jones wrote: > > On Mon, 27 Jul 2015, Dmitry Torokhov wrote: -> > +> >=20 > > > On Mon, Jul 27, 2015 at 03:43:00PM -0700, Dmitry Torokhov wrote: > > > > On Thu, Jul 23, 2015 at 05:17:41PM +0100, S Twiss wrote: > > > > > From: S Twiss <stwiss.opensource@diasemi.com> -> > > > > +> > > > >=20 > > > > > Add device tree bindings for the DA9062 OnKey driver component -> > > > > +> > > > >=20 > > > > > Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com> -> > > > > +> > > > >=20 > > > > > --- > > > > > Changes in V3: > > > > > - Child driver specifics separated out into separate document > > > > > in this case ../input/da9062-onkey.txt > > > > > Changes in V2: > > > > > - No change -> > > > > -> > > > > This patch applies against linux-next and next-20150708 -> > > > > -> > > > > -> > > > > .../devicetree/bindings/input/da9062-onkey.txt | 36 ++++++++++++++++++++++ +> > > > >=20 +> > > > > This patch applies against linux-next and next-20150708=20 +> > > > >=20 +> > > > >=20 +> > > > > .../devicetree/bindings/input/da9062-onkey.txt | 36 ++++++++= +++++++++++++++ > > > > > Documentation/devicetree/bindings/mfd/da9062.txt | 3 ++ -> > > > +> > > >=20 > > > > I dropped bits for mfd/da9062.txt, changed to mention both 9062 and > > > > 9063, folded into the onkey patch and applied. -> > > +> > >=20 > > > Argh, da9062 core is not in mainline yet... OK, below is the patch I -> > > had; if Lee does not pick it up I'll re-apply it when da9062 core hits +> > > had; if Lee does not pick it up I'll re-apply it when da9062 core hit= +s > > > mainline. -> > +> >=20 > > Hmm... that's annoying. You've put the patch below your signature > > '--', so my mailer cuts it off. -> +>=20 > OK, sorry, I'll make sure to put in before the signature next time. Appreciated. > > [pasting] -> > +> >=20 > > > Input: add DA9062 OnKey capability to DA9063 OnKey driver -> > > +> > >=20 > > > From: S Twiss <stwiss.opensource@diasemi.com> -> > > -> > > Add DA9062 OnKey support into the existing DA9063 OnKey driver component by -> > > using generic access tables for common register and bit mask definitions. -> > > -> > > The following change will add generic register and bit mask support to the +> > >=20 +> > > Add DA9062 OnKey support into the existing DA9063 OnKey driver compon= +ent by +> > > using generic access tables for common register and bit mask definiti= +ons. +> > >=20 +> > > The following change will add generic register and bit mask support t= +o the > > > DA9063 OnKey. -> > > +> > >=20 > > > The following alterations have been made to the DA9063 OnKey: -> > > +> > >=20 > > > - Addition of a da906x_chip_config structure to hold all > > > generic registers and bitmasks for this type of OnKey component. > > > - Addition of an struct of_device_id table for DA9063 and DA9062 > > > defaults -> > > - Refactoring functions to use struct da9063_onkey accesses to generic +> > > - Refactoring functions to use struct da9063_onkey accesses to generi= +c > > > registers/masks instead of using defines from registers.h > > > - Re-work of da9063_onkey_probe() to use of_match_node() and > > > dev_get_regmap() to provide initialisation of generic registers and > > > masks and access to regmap -> > > +> > >=20 > > > Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com> > > > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> > > > --- > > > .../devicetree/bindings/input/da9062-onkey.txt | 32 +++++ > > > drivers/input/misc/Kconfig | 8 + -> > > drivers/input/misc/da9063_onkey.c | 129 ++++++++++++++++---- +> > > drivers/input/misc/da9063_onkey.c | 129 ++++++++++= +++++++---- > > > 3 files changed, 140 insertions(+), 29 deletions(-) -> > > create mode 100644 Documentation/devicetree/bindings/input/da9062-onkey.txt -> > +> > > create mode 100644 Documentation/devicetree/bindings/input/da9062-on= +key.txt +> > =20 > > I'm confused. What's the dependency? -> > +> >=20 > > There shouldn't be any issue applying input patches, just because > > there isn't an MFD counterpart. In fact, I would take prior > > acceptance of the child into consideration (would be like a +1 vote) > > when reviewing the MFD part. -> +>=20 > It's this chunk: -> +>=20 > +#include <linux/mfd/da9062/core.h> > +#include <linux/mfd/da9062/registers.h> -> +>=20 > and these header files are not in mainline yet. Ah, thanks for the clarification. @@ -91,11 +99,11 @@ I will apply the other patches. > > One suggestion however, I would ask for the DT binding and the driver > > to be separated, as per [0]. -> > +> >=20 > > [0] Documentation/devicetree/bindings/submitting-patches.txt -> +>=20 > Right, but that says about submitting patches, not applying them ;) -> +>=20 > When I chatted with Grant he said that the policy of separating binding > and code into separate patches is done so not to overwhelm devicetree > list and that is is perfectly fine to actually apply them as a single @@ -104,12 +112,21 @@ I will apply the other patches. Got you. :) --- +--=20 Lee Jones Linaro STMicroelectronics Landing Team Lead -Linaro.org │ Open source software for ARM SoCs +Linaro.org =E2=94=82 Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog --- -To unsubscribe from this list: send the line "unsubscribe linux-input" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html + +--=20 +--=20 +You received this message because you are subscribed to "rtc-linux". +Membership options at http://groups.google.com/group/rtc-linux . +Please read http://groups.google.com/group/rtc-linux/web/checklist +before submitting a driver. +---=20 +You received this message because you are subscribed to the Google Groups "= +rtc-linux" group. +To unsubscribe from this group and stop receiving emails from it, send an e= +mail to rtc-linux+unsubscribe@googlegroups.com. +For more options, visit https://groups.google.com/d/optout. diff --git a/a/content_digest b/N1/content_digest index de3717e..b7fabba 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,7 +5,7 @@ "ref\020150728084019.GM14943@x1\0" "ref\020150728172018.GB19610@dtor-ws\0" "From\0Lee Jones <lee.jones@linaro.org>\0" - "Subject\0Re: [PATCH V3 3/3] devicetree: da9062: Add device tree bindings for DA9062 OnKey\0" + "Subject\0[rtc-linux] Re: [PATCH V3 3/3] devicetree: da9062: Add device tree bindings for DA9062 OnKey\0" "Date\0Tue, 28 Jul 2015 18:30:58 +0100\0" "To\0Dmitry Torokhov <dmitry.torokhov@gmail.com>\0" "Cc\0S Twiss <stwiss.opensource@diasemi.com>" @@ -27,87 +27,95 @@ "\n" "> On Tue, Jul 28, 2015 at 09:40:19AM +0100, Lee Jones wrote:\n" "> > On Mon, 27 Jul 2015, Dmitry Torokhov wrote:\n" - "> > \n" + "> >=20\n" "> > > On Mon, Jul 27, 2015 at 03:43:00PM -0700, Dmitry Torokhov wrote:\n" "> > > > On Thu, Jul 23, 2015 at 05:17:41PM +0100, S Twiss wrote:\n" "> > > > > From: S Twiss <stwiss.opensource@diasemi.com>\n" - "> > > > > \n" + "> > > > >=20\n" "> > > > > Add device tree bindings for the DA9062 OnKey driver component\n" - "> > > > > \n" + "> > > > >=20\n" "> > > > > Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com>\n" - "> > > > > \n" + "> > > > >=20\n" "> > > > > ---\n" "> > > > > Changes in V3:\n" "> > > > > - Child driver specifics separated out into separate document\n" "> > > > > in this case ../input/da9062-onkey.txt\n" "> > > > > Changes in V2:\n" "> > > > > - No change\n" - "> > > > > \n" - "> > > > > This patch applies against linux-next and next-20150708 \n" - "> > > > > \n" - "> > > > > \n" - "> > > > > .../devicetree/bindings/input/da9062-onkey.txt | 36 ++++++++++++++++++++++\n" + "> > > > >=20\n" + "> > > > > This patch applies against linux-next and next-20150708=20\n" + "> > > > >=20\n" + "> > > > >=20\n" + "> > > > > .../devicetree/bindings/input/da9062-onkey.txt | 36 ++++++++=\n" + "++++++++++++++\n" "> > > > > Documentation/devicetree/bindings/mfd/da9062.txt | 3 ++\n" - "> > > > \n" + "> > > >=20\n" "> > > > I dropped bits for mfd/da9062.txt, changed to mention both 9062 and\n" "> > > > 9063, folded into the onkey patch and applied.\n" - "> > > \n" + "> > >=20\n" "> > > Argh, da9062 core is not in mainline yet... OK, below is the patch I\n" - "> > > had; if Lee does not pick it up I'll re-apply it when da9062 core hits\n" + "> > > had; if Lee does not pick it up I'll re-apply it when da9062 core hit=\n" + "s\n" "> > > mainline.\n" - "> > \n" + "> >=20\n" "> > Hmm... that's annoying. You've put the patch below your signature\n" "> > '--', so my mailer cuts it off.\n" - "> \n" + ">=20\n" "> OK, sorry, I'll make sure to put in before the signature next time.\n" "\n" "Appreciated.\n" "\n" "> > [pasting]\n" - "> > \n" + "> >=20\n" "> > > Input: add DA9062 OnKey capability to DA9063 OnKey driver\n" - "> > > \n" + "> > >=20\n" "> > > From: S Twiss <stwiss.opensource@diasemi.com>\n" - "> > > \n" - "> > > Add DA9062 OnKey support into the existing DA9063 OnKey driver component by\n" - "> > > using generic access tables for common register and bit mask definitions.\n" - "> > > \n" - "> > > The following change will add generic register and bit mask support to the\n" + "> > >=20\n" + "> > > Add DA9062 OnKey support into the existing DA9063 OnKey driver compon=\n" + "ent by\n" + "> > > using generic access tables for common register and bit mask definiti=\n" + "ons.\n" + "> > >=20\n" + "> > > The following change will add generic register and bit mask support t=\n" + "o the\n" "> > > DA9063 OnKey.\n" - "> > > \n" + "> > >=20\n" "> > > The following alterations have been made to the DA9063 OnKey:\n" - "> > > \n" + "> > >=20\n" "> > > - Addition of a da906x_chip_config structure to hold all\n" "> > > generic registers and bitmasks for this type of OnKey component.\n" "> > > - Addition of an struct of_device_id table for DA9063 and DA9062\n" "> > > defaults\n" - "> > > - Refactoring functions to use struct da9063_onkey accesses to generic\n" + "> > > - Refactoring functions to use struct da9063_onkey accesses to generi=\n" + "c\n" "> > > registers/masks instead of using defines from registers.h\n" "> > > - Re-work of da9063_onkey_probe() to use of_match_node() and\n" "> > > dev_get_regmap() to provide initialisation of generic registers and\n" "> > > masks and access to regmap\n" - "> > > \n" + "> > >=20\n" "> > > Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com>\n" "> > > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\n" "> > > ---\n" "> > > .../devicetree/bindings/input/da9062-onkey.txt | 32 +++++\n" "> > > drivers/input/misc/Kconfig | 8 +\n" - "> > > drivers/input/misc/da9063_onkey.c | 129 ++++++++++++++++----\n" + "> > > drivers/input/misc/da9063_onkey.c | 129 ++++++++++=\n" + "++++++----\n" "> > > 3 files changed, 140 insertions(+), 29 deletions(-)\n" - "> > > create mode 100644 Documentation/devicetree/bindings/input/da9062-onkey.txt\n" - "> > \n" + "> > > create mode 100644 Documentation/devicetree/bindings/input/da9062-on=\n" + "key.txt\n" + "> > =20\n" "> > I'm confused. What's the dependency?\n" - "> > \n" + "> >=20\n" "> > There shouldn't be any issue applying input patches, just because\n" "> > there isn't an MFD counterpart. In fact, I would take prior\n" "> > acceptance of the child into consideration (would be like a +1 vote)\n" "> > when reviewing the MFD part.\n" - "> \n" + ">=20\n" "> It's this chunk:\n" - "> \n" + ">=20\n" "> +#include <linux/mfd/da9062/core.h>\n" "> +#include <linux/mfd/da9062/registers.h>\n" - "> \n" + ">=20\n" "> and these header files are not in mainline yet.\n" "\n" "Ah, thanks for the clarification.\n" @@ -116,11 +124,11 @@ "\n" "> > One suggestion however, I would ask for the DT binding and the driver\n" "> > to be separated, as per [0].\n" - "> > \n" + "> >=20\n" "> > [0] Documentation/devicetree/bindings/submitting-patches.txt\n" - "> \n" + ">=20\n" "> Right, but that says about submitting patches, not applying them ;)\n" - "> \n" + ">=20\n" "> When I chatted with Grant he said that the policy of separating binding\n" "> and code into separate patches is done so not to overwhelm devicetree\n" "> list and that is is perfectly fine to actually apply them as a single\n" @@ -129,14 +137,23 @@ "\n" "Got you. :)\n" "\n" - "-- \n" + "--=20\n" "Lee Jones\n" "Linaro STMicroelectronics Landing Team Lead\n" - "Linaro.org \342\224\202 Open source software for ARM SoCs\n" + "Linaro.org =E2=94=82 Open source software for ARM SoCs\n" "Follow Linaro: Facebook | Twitter | Blog\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-input\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + "\n" + "--=20\n" + "--=20\n" + "You received this message because you are subscribed to \"rtc-linux\".\n" + "Membership options at http://groups.google.com/group/rtc-linux .\n" + "Please read http://groups.google.com/group/rtc-linux/web/checklist\n" + "before submitting a driver.\n" + "---=20\n" + "You received this message because you are subscribed to the Google Groups \"=\n" + "rtc-linux\" group.\n" + "To unsubscribe from this group and stop receiving emails from it, send an e=\n" + "mail to rtc-linux+unsubscribe@googlegroups.com.\n" + For more options, visit https://groups.google.com/d/optout. -9902b735a409ef26cb6d90ad4c78db78f877e6b065f13040d878fb253dc6732c +295dc9fe1795f810419719fd6745e84c7e070e6311c82963b49bc8c2d46c0171
diff --git a/a/1.txt b/N2/1.txt index e422d4a..035fc68 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -109,7 +109,3 @@ Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog --- -To unsubscribe from this list: send the line "unsubscribe linux-input" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N2/content_digest index de3717e..4bdb4f9 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -133,10 +133,6 @@ "Lee Jones\n" "Linaro STMicroelectronics Landing Team Lead\n" "Linaro.org \342\224\202 Open source software for ARM SoCs\n" - "Follow Linaro: Facebook | Twitter | Blog\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-input\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + Follow Linaro: Facebook | Twitter | Blog -9902b735a409ef26cb6d90ad4c78db78f877e6b065f13040d878fb253dc6732c +0726c0f88b483f4c4c0fef3107d48e3e3bfc89a80cfc834dc82317a2a781a7cc
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.