linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org, "Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy.shevchenko@gmail.com>,
	"Matt Ranostay" <matt.ranostay@konsulko.com>,
	"Lars-Peter Clausen" <lars@metafoo.de>
Cc: Alexandru Ardelean <alexandru.ardelean@analog.com>
Subject: IIO: Review request.
Date: Fri, 18 Sep 2020 13:33:57 +0100	[thread overview]
Message-ID: <20200918133357.0ed56512@archlinux> (raw)

Hi All,

Classic being the maintainer problem, is that there is no one specific to pester
when you can't get reviews on your own patches.  Hence if anyone has some
time I'd appreciate sanity checks on:

[PATCH 2/3] iio: Add __printf() attributes to various allocation functions
https://lore.kernel.org/linux-iio/20200913132115.800131-3-jic23@kernel.org/

[PATCH 3/3] iio:core: Tidy up kernel-doc.
https://lore.kernel.org/linux-iio/20200913132115.800131-4-jic23@kernel.org/

[PATCH] iio:magn:hmc5843: Fix passing true where iio_shared_by enum required.
https://lore.kernel.org/linux-iio/20200913112546.715624-1-jic23@kernel.org/

[PATCH] iio:accel:bma180: Fix use of true when should be iio_shared_by enum
https://lore.kernel.org/linux-iio/20200913121227.764626-1-jic23@kernel.org/

For those last 2 I forgot I'd previously sent effectively the same fixes out
earlier in the year but didn't get any reviews then either :(

Note I've randomly picked a few people who have done reviews or posted a lot
of patches recently for the cc list.  I'm more than happy if anyone else
wants to join in with the fun :)  Reviews are always appreciated for any
code submitted to IIO from anyone.  If you are unsure about something in
a review, it is fine to say so.  Hence even relatively new people can
offer great value.  We all started somewhere!

Thanks,

Jonathan

             reply	other threads:[~2020-09-18 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 12:33 Jonathan Cameron [this message]
2020-09-18 14:05 ` IIO: Review request Andy Shevchenko
2020-09-18 15:05   ` Jonathan Cameron

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=20200918133357.0ed56512@archlinux \
    --to=jic23@kernel.org \
    --cc=alexandru.ardelean@analog.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=matt.ranostay@konsulko.com \
    --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;
as well as URLs for NNTP newsgroup(s).