Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: William Breathitt Gray <william.gray@linaro.org>
Cc: lars@metafoo.de, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v2] iio: dac: cio-dac: Migrate to the regmap API
Date: Sat, 18 Mar 2023 16:43:47 +0000	[thread overview]
Message-ID: <20230318164347.1e96325c@jic23-huawei> (raw)
In-Reply-To: <ZAzQ6LyfllSjN16j@fedora>

On Sat, 11 Mar 2023 14:05:12 -0500
William Breathitt Gray <william.gray@linaro.org> wrote:

> On Sat, Mar 11, 2023 at 06:57:19PM +0000, Jonathan Cameron wrote:
> > On Sat, 11 Mar 2023 09:02:18 -0500
> > William Breathitt Gray <william.gray@linaro.org> wrote:  
> > > diff --git a/drivers/iio/dac/cio-dac.c b/drivers/iio/dac/cio-dac.c
> > > index 791dd999cf29..759833a6bd29 100644
> > > --- a/drivers/iio/dac/cio-dac.c
> > > +++ b/drivers/iio/dac/cio-dac.c
> > > @@ -6,16 +6,15 @@
> > >   * This driver supports the following Measurement Computing devices: CIO-DAC16,
> > >   * CIO-DAC06, and PC104-DAC06.
> > >   */
> > > -#include <linux/bitops.h>
> > > +#include <linux/bits.h>  
> > 
> > I'm not immediately spotting why this change is part of the regmap
> > conversion.
> > 
> > It may well make sense, but if unrelated, should probably be in a different patch.  
> 
> No you're right, this is an unrelated cleanup that I should probably
> have pulled out to its own dedicated patch. If there is a need for a v3,
> I'll split this off and submit it separately.
> 
Not other comments, so meh. I've had my moan :)

Applied to the togreg branch of iio.git and pushed out as testing for 0-day
to see if it can find anything we missed.

Thanks,

Jonathan

> William Breathitt Gray


      reply	other threads:[~2023-03-18 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 14:02 [PATCH v2] iio: dac: cio-dac: Migrate to the regmap API William Breathitt Gray
2023-03-11 18:57 ` Jonathan Cameron
2023-03-11 19:05   ` William Breathitt Gray
2023-03-18 16:43     ` 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=20230318164347.1e96325c@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=william.gray@linaro.org \
    /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