All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Cc: dragos.bogdan@analog.com, alexandru.ardelean@analog.com,
	linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	kernel-usp@googlegroups.com
Subject: Re: [PATCH v2 1/2] iio: adc: Add driver support for AD7292
Date: Sun, 27 Oct 2019 09:28:45 +0000	[thread overview]
Message-ID: <20191027092845.5a1269f5@archlinux> (raw)
In-Reply-To: <20191022142736.ztch3mzqpv6jcvhm@smtp.gmail.com>

On Tue, 22 Oct 2019 11:27:37 -0300
Marcelo Schmitt <marcelo.schmitt1@gmail.com> wrote:

> Hi Jonathan,
> 
> Should I send a V3 for the whole patchset or just for the DT binding patch?

Always send whole patch sets.  It's far too fiddly to track down parts
from different versions.

Thanks,

Jonathan

> 
> Thanks,
> 
> Marcelo
> 
> On 10/21, Jonathan Cameron wrote:
> > On Tue, 15 Oct 2019 23:51:22 -0300
> > Marcelo Schmitt <marcelo.schmitt1@gmail.com> wrote:
> >   
> > > The AD7292 is a 10-bit monitor and control system with ADC, DACs,
> > > temperature sensor, and GPIOs.
> > > 
> > > Configure AD7292 devices in direct access mode, enabling single-ended
> > > ADC readings.
> > > 
> > > Datasheet:
> > > Link: https://www.analog.com/media/en/technical-documentation/data-sheets/ad7292.pdf
> > > 
> > > Signed-off-by: Marcelo Schmitt <marcelo.schmitt1@gmail.com>  
> > This looks fine to me.
> > 
> > Assuming nothing else comes up, I'll pick this up once the binding was tidied up.
> > 
> > Thanks,
> > 
> > Jonathan
> >   


      reply	other threads:[~2019-10-27  9:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16  2:51 [PATCH v2 1/2] iio: adc: Add driver support for AD7292 Marcelo Schmitt
2019-10-21 17:06 ` Jonathan Cameron
2019-10-22 14:27   ` Marcelo Schmitt
2019-10-27  9:28     ` Jonathan Cameron [this message]

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=20191027092845.5a1269f5@archlinux \
    --to=jic23@kernel.org \
    --cc=alexandru.ardelean@analog.com \
    --cc=dragos.bogdan@analog.com \
    --cc=kernel-usp@googlegroups.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.schmitt1@gmail.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 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.