Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: linux-iio <linux-iio@vger.kernel.org>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH 0/4] staging: iio: DMA alignment fixes.
Date: Sat, 13 Aug 2022 17:01:34 +0100	[thread overview]
Message-ID: <20220813170134.77e08da6@jic23-huawei> (raw)
In-Reply-To: <CAHp75VejHmUx_PkoKfijcmVdZWdEvXtKwVWTTPy9uadB559FcA@mail.gmail.com>

On Mon, 8 Aug 2022 11:20:32 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:

> On Sun, Aug 7, 2022 at 5:37 PM Jonathan Cameron <jic23@kernel.org> wrote:
> >
> > From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> >
> > When I introduced IIO_DMA_MINALIGN and applied it to all the drivers
> > in drivers/iio I said I'd swing by the few remaining staging drivers
> > at a later date. This set fixes those staging/iio drivers.
> >
> > Note that no one has been very active on these drivers for some time.
> > They do however support parts that are still available (and I have
> > at least one of them) so I think it's worth keeping them around for now.
> > Perhaps the necessary cleanup work can be done against emulation or
> > road test or we can get parts for anyone interested in doing the necessary
> > work.
> >
> > Anyhow, upshot is that it's unlikely anyone will feel ownership of these
> > drivers enough to review this series so if anyone has time a quick
> > glance over it would be much appreciated!  
> 
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> 
> for non-commented patches.
> 
Thanks, patches 2-4 applied. v2 of patch one to be posted shortly.

Jonathan



      reply	other threads:[~2022-08-13 15:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-07 15:12 [PATCH 0/4] staging: iio: DMA alignment fixes Jonathan Cameron
2022-08-07 15:12 ` [PATCH 1/4] staging: iio: frequency: ad9832: Fix alignment for DMA safety Jonathan Cameron
2022-08-08  9:18   ` Andy Shevchenko
2022-08-08 14:14     ` Jonathan Cameron
2022-08-07 15:12 ` [PATCH 2/4] staging: iio: frequency: ad9834: " Jonathan Cameron
2022-08-07 15:12 ` [PATCH 3/4] staging: iio: meter: ade7854: " Jonathan Cameron
2022-08-07 15:12 ` [PATCH 4/4] staging: iio: resolver: ad2s1210: " Jonathan Cameron
2022-08-08  9:20 ` [PATCH 0/4] staging: iio: DMA alignment fixes Andy Shevchenko
2022-08-13 16:01   ` 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=20220813170134.77e08da6@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=nuno.sa@analog.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