linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Subject: iio: Request for review.  Warning fix patches.
Date: Sun, 3 Nov 2019 12:56:53 +0000	[thread overview]
Message-ID: <20191103125653.57ccd98f@archlinux> (raw)

Hi All,

Whilst I 'could' just take my own patches without review, I know
I can sometimes make stupid mistakes so would like to get some eyes
and formal tags on the following:

[PATCH] iio:adc:ti-adc084s021: Endian casting tidy ups.
[PATCH] iio: adc: aspeed: use devm_platform_ioremap_resource
[PATCH] iio: adc: mt6577_auxdac: use devm_platform_ioremap_resource
[PATCH] iio: adc: bcm_iproc_adc: drop a stray semicolon
[PATCH] iio: adc: cc10001: use devm_platform_ioremap_resource
[PATCH] iio: adc: ingenic: Use devm_platform_ioremap_resource
[PATCH] iio: adc: lpc18xx: use devm_platform_ioremap_resource
[PATCH] iio: adc: npcm: use devm_platform_ioremap_resource
[PATCH] iio: adc: rcar-gyroadc: use devm_platform_ioremap_resource
[PATCH] iio: adc: spear_adc: Use devm_platform_ioremap_resource
[PATCH] iio: adc: vf610: use devm_platform_ioremap_resource
[PATCH] iio: dac: lpc18xx: Use devm_platform_ioremap_resource
[PATCH] iio: dac: vf610: Use devm_platform_ioremap_resource

I suspect most if not all of the original authors are no longer
working with these.   Note that these are all simple patches,
so a good opportunity for less experienced reviewers to get
involved alongside the old hands!

I think getting all of those merged should give us clean builds
with sparse and coccicheck which will make it easier to spot
new issues in the future.  They are all nicely little cleanups
even without that target.

Thanks,

Jonathan

                 reply	other threads:[~2019-11-03 12:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20191103125653.57ccd98f@archlinux \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).