From: maitysanchayan@gmail.com
To: Jonathan Cameron <jic23@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
linux-iio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, shawnguo@kernel.org, stefan@agner.ch,
pmeerw@pmeerw.net
Subject: Re: [PATCH v3 2/2] iio: dac: vf610_dac: Add IIO DAC driver for Vybrid SoC
Date: Thu, 25 Feb 2016 21:00:45 +0530 [thread overview]
Message-ID: <20160225153045.GA15913@Sanchayan-Arch> (raw)
In-Reply-To: <56CE18AC.6020603@kernel.org>
Hello,
On 16-02-24 20:55:08, Jonathan Cameron wrote:
> On 23/02/16 20:54, Rob Herring wrote:
> > On Mon, Feb 22, 2016 at 11:48:37AM +0530, Sanchayan Maity wrote:
> >> Add driver support for DAC peripheral on Vybrid SoC.
> >>
> >> Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
> >> ---
> >> Documentation/ABI/testing/sysfs-bus-iio-vf610 | 9 +
> >> .../devicetree/bindings/iio/dac/vf610-dac.txt | 20 ++
> >
> > For the binding:
> >
> > Acked-by: Rob Herring <robh@kernel.org>
> Applied to the togreg branch of iio.git - initially pushed out as testing
> for the autobuilders to play with it.
Thanks Jonathan.
>
> Note the dts change probably wants to go via the relevant arch trees.
> I can take it with an appropriate ack if not.
Generally shawn picks up the device tree changes once the driver makes
it to his for-next branch. I will ping shawn to pick this up once the
driver lands in shawn's for-next branch.
Regards,
Sanchayan.
next prev parent reply other threads:[~2016-02-25 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 6:18 [PATCH v3 0/2] Add DAC driver support for Vybrid SoC Sanchayan Maity
2016-02-22 6:18 ` [PATCH v3 1/2] ARM: dts: vfxxx: Add DAC node " Sanchayan Maity
2016-02-22 6:18 ` [PATCH v3 2/2] iio: dac: vf610_dac: Add IIO DAC driver " Sanchayan Maity
2016-02-23 20:54 ` Rob Herring
2016-02-24 20:55 ` Jonathan Cameron
2016-02-25 15:30 ` maitysanchayan [this message]
2016-02-29 3:23 ` Shawn Guo
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=20160225153045.GA15913@Sanchayan-Arch \
--to=maitysanchayan@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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).