From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: linux-iio <linux-iio@vger.kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH 0/2] IIO: Clean up a couple of warnings that snuck in.
Date: Sat, 13 Aug 2022 16:57:58 +0100 [thread overview]
Message-ID: <20220813165758.5050b84e@jic23-huawei> (raw)
In-Reply-To: <CAHp75VehuNsXbNO0qW0aYZqZcmAR3VbOR_zQQurhNxyLUtiWeA@mail.gmail.com>
On Mon, 8 Aug 2022 11:15:52 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> On Sun, Aug 7, 2022 at 4:50 PM Jonathan Cameron <jic23@kernel.org> wrote:
> >
> > From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> >
> > I'm not sure how these slipped through my local tests and 0-day.
> > These are definitely shown with W=1, perhaps not without that
> > but IIO is generally W=1 clean.
>
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Applied. Thanks,
Jonathan
>
> > Jonathan Cameron (2):
> > iio: test: Mark file local structure arrays static.
> > iio: light: cm32181: Mark the dev_pm_ops static.
> >
> > drivers/iio/light/cm32181.c | 2 +-
> > drivers/iio/test/iio-test-rescale.c | 4 ++--
> > 2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > --
> > 2.37.1
> >
>
>
prev parent reply other threads:[~2022-08-13 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 14:54 [PATCH 0/2] IIO: Clean up a couple of warnings that snuck in Jonathan Cameron
2022-08-07 14:54 ` [PATCH 1/2] iio: test: Mark file local structure arrays static Jonathan Cameron
2022-08-07 15:52 ` Liam Beguin
2022-08-07 14:54 ` [PATCH 2/2] iio: light: cm32181: Mark the dev_pm_ops static Jonathan Cameron
2022-08-08 9:15 ` [PATCH 0/2] IIO: Clean up a couple of warnings that snuck in Andy Shevchenko
2022-08-13 15:57 ` 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=20220813165758.5050b84e@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=andy.shevchenko@gmail.com \
--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).