From: Lee Jones <lee.jones@linaro.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Opensource [Steve Twiss]" <stwiss.opensource@diasemi.com>,
DEVICETREE <devicetree@vger.kernel.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
LINUXINPUT <linux-input@vger.kernel.org>,
LINUXKERNEL <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <pawel.moll@arm.com>,
RTCLINUX <rtc-linux@googlegroups.com>,
Rob Herring <robh+dt@kernel.org>,
David Dajun Chen <david.chen@diasemi.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Support Opensource <Support.Opensource@diasemi.com>
Subject: Re: [PATCH V3 3/3] devicetree: da9062: Add device tree bindings for DA9062 OnKey
Date: Wed, 30 Sep 2015 12:47:17 +0100 [thread overview]
Message-ID: <20150930114717.GB27197@x1> (raw)
In-Reply-To: <20150929235408.GC29469@dtor-ws>
On Tue, 29 Sep 2015, Dmitry Torokhov wrote:
> On Mon, Sep 28, 2015 at 08:19:27AM +0000, Opensource [Steve Twiss] wrote:
> >
> > > Subject: Re: [PATCH V3 3/3] devicetree: da9062: Add device tree bindings for DA9062 OnKey
> > >
> > > 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>
> > > > >
> > > > > Add device tree bindings for the DA9062 OnKey driver component
> > > > >
> > > > > Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com>
> > > > >
> > > > > ---
> > > > > 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
> > > ++++++++++++++++++++++
> > > > > Documentation/devicetree/bindings/mfd/da9062.txt | 3 ++
> > > >
> > > > I dropped bits for mfd/da9062.txt, changed to mention both 9062 and
> > > > 9063, folded into the onkey patch and applied.
> > >
> > > 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
> > > mainline.
> > >
> >
> > Hi Lee and Dmitry,
> >
> > This patch seems to have been missed. It is the main OnKey driver for DA9062 and this
> > component was waiting for the DA9062 MFD core to make it into linux-mainline/v4.3-rc1.
> >
> > Is there any reply on this yet please? There just seems to be a little patch administration
> > problem holding things up.
>
> I queued it for 4.4.
Thanks Dmitry.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-09-30 11:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 16:17 [PATCH V3 0/3] da9062: Add DA9062 OnKey support using the existing DA9063 OnKey driver S Twiss
2015-07-23 16:17 ` [PATCH V3 1/3] mfd: da9062: Support for the DA9063 OnKey in the DA9062 core S Twiss
2015-07-28 8:42 ` Lee Jones
2015-07-23 16:17 ` [PATCH V3 2/3] onkey: da9063: Add DA9062 OnKey capability to DA9063 OnKey driver S Twiss
2015-09-15 7:57 ` Stephen Twiss
2015-09-15 8:08 ` Opensource [Steve Twiss]
2015-07-23 16:17 ` [PATCH V3 3/3] devicetree: da9062: Add device tree bindings for DA9062 OnKey S Twiss
2015-07-27 22:43 ` Dmitry Torokhov
2015-07-28 5:40 ` Dmitry Torokhov
2015-07-28 7:42 ` Lee Jones
2015-07-28 7:44 ` Opensource [Steve Twiss]
2015-07-28 7:42 ` Opensource [Steve Twiss]
2015-07-28 8:40 ` Lee Jones
2015-07-28 17:20 ` Dmitry Torokhov
2015-07-28 17:30 ` Lee Jones
2015-09-28 8:19 ` Opensource [Steve Twiss]
2015-09-29 23:54 ` Dmitry Torokhov
2015-09-30 7:45 ` Opensource [Steve Twiss]
2015-09-30 11:47 ` Lee Jones [this message]
2015-07-28 8:41 ` Lee Jones
2015-07-28 8:52 ` [PATCH V3 0/3] da9062: Add DA9062 OnKey support using the existing DA9063 OnKey driver Lee Jones
2015-07-28 14:09 ` Opensource [Steve Twiss]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150930114717.GB27197@x1 \
--to=lee.jones@linaro.org \
--cc=Support.Opensource@diasemi.com \
--cc=david.chen@diasemi.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sameo@linux.intel.com \
--cc=stwiss.opensource@diasemi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).