All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: maitysanchayan@gmail.com
Cc: Jonathan Cameron <jic23@kernel.org>,
	Rob Herring <robh@kernel.org>,
	linux-iio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.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: Mon, 29 Feb 2016 11:23:42 +0800	[thread overview]
Message-ID: <20160229032342.GR22051@tiger> (raw)
In-Reply-To: <20160225153045.GA15913@Sanchayan-Arch>

On Thu, Feb 25, 2016 at 09:00:45PM +0530, maitysanchayan@gmail.com wrote:
> 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.

For such device enabling which does no harm on my tree, i.e. no
regression or breakage, I will be happy to take it once driver part gets
applied, so that we do not need to wait for another release cycle to
get it work.

I applied dts patch, thanks.

Shawn

WARNING: multiple messages have this Message-ID (diff)
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] iio: dac: vf610_dac: Add IIO DAC driver for Vybrid SoC
Date: Mon, 29 Feb 2016 11:23:42 +0800	[thread overview]
Message-ID: <20160229032342.GR22051@tiger> (raw)
In-Reply-To: <20160225153045.GA15913@Sanchayan-Arch>

On Thu, Feb 25, 2016 at 09:00:45PM +0530, maitysanchayan at gmail.com wrote:
> 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.

For such device enabling which does no harm on my tree, i.e. no
regression or breakage, I will be happy to take it once driver part gets
applied, so that we do not need to wait for another release cycle to
get it work.

I applied dts patch, thanks.

Shawn

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	stefan-XLVq0VzYD2Y@public.gmane.org,
	pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org
Subject: Re: [PATCH v3 2/2] iio: dac: vf610_dac: Add IIO DAC driver for Vybrid SoC
Date: Mon, 29 Feb 2016 11:23:42 +0800	[thread overview]
Message-ID: <20160229032342.GR22051@tiger> (raw)
In-Reply-To: <20160225153045.GA15913@Sanchayan-Arch>

On Thu, Feb 25, 2016 at 09:00:45PM +0530, maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
> 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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > >> ---
> > >>  Documentation/ABI/testing/sysfs-bus-iio-vf610      |   9 +
> > >>  .../devicetree/bindings/iio/dac/vf610-dac.txt      |  20 ++
> > > 
> > > For the binding:
> > > 
> > > Acked-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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.

For such device enabling which does no harm on my tree, i.e. no
regression or breakage, I will be happy to take it once driver part gets
applied, so that we do not need to wait for another release cycle to
get it work.

I applied dts patch, thanks.

Shawn

  reply	other threads:[~2016-02-29  3:23 UTC|newest]

Thread overview: 21+ 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 ` Sanchayan Maity
2016-02-22  6:18 ` Sanchayan Maity
2016-02-22  6:18 ` [PATCH v3 1/2] ARM: dts: vfxxx: Add DAC node " Sanchayan Maity
2016-02-22  6:18   ` Sanchayan Maity
2016-02-22  6:18   ` Sanchayan Maity
2016-02-22  6:18 ` [PATCH v3 2/2] iio: dac: vf610_dac: Add IIO DAC driver " Sanchayan Maity
2016-02-22  6:18   ` Sanchayan Maity
2016-02-22  6:18   ` Sanchayan Maity
2016-02-23 20:54   ` Rob Herring
2016-02-23 20:54     ` Rob Herring
2016-02-23 20:54     ` Rob Herring
2016-02-24 20:55     ` Jonathan Cameron
2016-02-24 20:55       ` Jonathan Cameron
2016-02-24 20:55       ` Jonathan Cameron
2016-02-25 15:30       ` maitysanchayan
2016-02-25 15:30         ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
2016-02-25 15:30         ` maitysanchayan at gmail.com
2016-02-29  3:23         ` Shawn Guo [this message]
2016-02-29  3:23           ` Shawn Guo
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=20160229032342.GR22051@tiger \
    --to=shawnguo@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=maitysanchayan@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh@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 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.