From: Jonathan Cameron <jic23@kernel.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Alexandru Tachici <alexandru.tachici@analog.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Michael Hennerich <michael.hennerich@analog.com>,
Saravanan Sekar <sravanhome@gmail.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Linus Walleij <linus.walleij@linaro.org>,
Vincent Pelletier <plr.vincent@gmail.com>,
linux-kernel@vger.kernel.org,
Beniamin Bia <beniamin.bia@analog.com>,
linux-iio@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Hartmut Knaack <knaack.h@gmx.de>,
linux-rockchip@lists.infradead.org,
Alexandru Ardelean <alexandru.ardelean@analog.com>,
Alex Dewar <alex.dewar90@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Artur Rojek <contact@artur-rojek.eu>
Subject: Re: [PATCH] iio: adc: rockchip_saradc: Allow compile-testing with !ARM
Date: Sun, 6 Sep 2020 14:27:21 +0100 [thread overview]
Message-ID: <20200906142721.73a533dd@archlinux> (raw)
In-Reply-To: <1602652.ZmzXO7uU3z@diego>
On Fri, 04 Sep 2020 19:32:22 +0200
Heiko Stübner <heiko@sntech.de> wrote:
> Am Freitag, 4. September 2020, 19:04:16 CEST schrieb Alex Dewar:
> > There seems no reason to allow for compile-testing on ARM only, so
> > remove this restriction.
> >
> > Build-tested with allyesconfig on x86.
> >
> > Signed-off-by: Alex Dewar <alex.dewar90@gmail.com>
>
> Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to poke at it and see if we missed anything.
Thanks,
Jonathan
>
> > ---
> > drivers/iio/adc/Kconfig | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/adc/Kconfig b/drivers/iio/adc/Kconfig
> > index d94dc800b842..03929606bb01 100644
> > --- a/drivers/iio/adc/Kconfig
> > +++ b/drivers/iio/adc/Kconfig
> > @@ -863,7 +863,7 @@ config RN5T618_ADC
> >
> > config ROCKCHIP_SARADC
> > tristate "Rockchip SARADC driver"
> > - depends on ARCH_ROCKCHIP || (ARM && COMPILE_TEST)
> > + depends on ARCH_ROCKCHIP || COMPILE_TEST
> > depends on RESET_CONTROLLER
> > select IIO_BUFFER
> > select IIO_TRIGGERED_BUFFER
> >
>
>
>
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2020-09-06 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 17:04 [PATCH] iio: adc: rockchip_saradc: Allow compile-testing with !ARM Alex Dewar
2020-09-04 17:32 ` Heiko Stübner
2020-09-06 13:27 ` 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=20200906142721.73a533dd@archlinux \
--to=jic23@kernel.org \
--cc=alex.dewar90@gmail.com \
--cc=alexandru.ardelean@analog.com \
--cc=alexandru.tachici@analog.com \
--cc=andy.shevchenko@gmail.com \
--cc=beniamin.bia@analog.com \
--cc=contact@artur-rojek.eu \
--cc=heiko@sntech.de \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.hennerich@analog.com \
--cc=miquel.raynal@bootlin.com \
--cc=p.zabel@pengutronix.de \
--cc=plr.vincent@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=sravanhome@gmail.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).