From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Wei Yongjun" <weiyongjun@huaweicloud.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Nuno Sá" <nuno.sa@analog.com>,
"Wei Yongjun" <weiyongjun1@huawei.com>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/5 v3] iio: adc: ti-ads131e08: Silence no spi_device_id warnings
Date: Thu, 22 Sep 2022 16:26:31 +0300 [thread overview]
Message-ID: <CAHp75Vfj_H27eHj-vkbTNJ4x+DVuccZCBRVH47KbBNOBzdntFQ@mail.gmail.com> (raw)
In-Reply-To: <20220922121321.000026ea@huawei.com>
On Thu, Sep 22, 2022 at 2:13 PM Jonathan Cameron
<Jonathan.Cameron@huawei.com> wrote:
> On Thu, 22 Sep 2022 07:43:34 +0200
> Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
...
> By providing the new table, non firmware registration paths are enabled
> that were not before (board files + I think Greybus still uses that path?)
> If those are used they will get NULL from device_get_match_data() with
> predictable bad results.
We still have some board files or board:ish info in the kernel to
support some platforms, so it won't go away (at least soon: in the
parentheses because don't forget about FPGAs that need a possibility
of the reconfiguration at run time).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-09-22 13:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 16:36 [PATCH 0/5 v3] iio: Silence no spi_device_id warnings Wei Yongjun
2022-09-21 16:36 ` [PATCH 1/5 v3] iio: adc: ti-ads131e08: " Wei Yongjun
2022-09-22 5:43 ` Uwe Kleine-König
2022-09-22 11:13 ` Jonathan Cameron
2022-09-22 13:26 ` Andy Shevchenko [this message]
2022-09-21 16:36 ` [PATCH 2/5 v3] iio: accel: sca3300: Silence no spi_device_id warning Wei Yongjun
2022-09-22 6:12 ` Tomas Melin
2022-09-21 16:36 ` [PATCH 3/5 v3] iio: adc: ad9467: Silence no spi_device_id warnings Wei Yongjun
2022-09-21 16:36 ` [PATCH 4/5 v3] iio: adc: ad7192: " Wei Yongjun
2022-09-21 16:36 ` [PATCH 5/5 v3] iio: adc: ad7124: " Wei Yongjun
2022-09-21 20:41 ` [PATCH 0/5 v3] iio: " Andy Shevchenko
2022-10-02 14:03 ` Jonathan Cameron
2022-10-03 7:29 ` Andy Shevchenko
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=CAHp75Vfj_H27eHj-vkbTNJ4x+DVuccZCBRVH47KbBNOBzdntFQ@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=weiyongjun1@huawei.com \
--cc=weiyongjun@huaweicloud.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).