From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>
Cc: "Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v1 1/1] at24: Drop of_match_ptr() and ACPI_PTR() protections
Date: Thu, 27 Feb 2025 09:18:30 +0100 [thread overview]
Message-ID: <f9b8acf8-7ed5-4d9f-84d1-acdbaa9e96d8@app.fastmail.com> (raw)
In-Reply-To: <Z78itKfsojtMpr_o@smile.fi.intel.com>
On Wed, Feb 26, 2025, at 15:18, Andy Shevchenko wrote:
> On Tue, Feb 25, 2025 at 06:21:29PM +0100, Krzysztof Kozlowski wrote:
>> On 25/02/2025 11:29, Arnd Bergmann wrote:
>>
>> I tried to fix this in SPI, regulator and ASoC 2 years ago and Mark
>> rejected such approach of dropping ACPI/of_match_ptr. AFAIU, Mark wants
>> this to be fixed in more generic way, on the OF and ACPI common code,
>> not per driver.
>>
>> SPI:
>> https://lore.kernel.org/all/7a65d775-cf07-4393-8b10-2cef4d5266ab@sirena.org.uk/
>>
>> regulator:
>> https://lore.kernel.org/all/20230310214553.275450-1-krzysztof.kozlowski@linaro.org/
>>
>> ASoC:
>> https://lore.kernel.org/all/20230310214333.274903-1-krzysztof.kozlowski@linaro.org/
>
> It was almost two years ago. Things may be changed :-)
> At least I have no impediments so far with converting drivers I'm supporting in
> the SPI. For ASoC there might be a new attempt by Cezary Rojewski in the future
> (he does some cleanups in that area, and we discussed cleaning up ACPI_PTR() at
> minimum).
I skipped those three subsystems when I sent my backlog. Comparing
what I have left with the version from the patches above I see
that about 40% of the warnings in all three are already addressed
in the meantime, leaving just
drivers/regulator/pbias-regulator.c | 2 +-
drivers/regulator/twl-regulator.c | 2 +-
drivers/regulator/twl6030-regulator.c | 2 +-
drivers/spi/spi-armada-3700.c | 2 +-
drivers/spi/spi-img-spfi.c | 2 +-
drivers/spi/spi-meson-spicc.c | 2 +-
drivers/spi/spi-meson-spifc.c | 2 +-
drivers/spi/spi-orion.c | 2 +-
drivers/spi/spi-pic32-sqi.c | 2 +-
drivers/spi/spi-pic32.c | 2 +-
drivers/spi/spi-rockchip.c | 2 +-
drivers/spi/spi-s3c64xx.c | 2 +-
drivers/spi/spi-st-ssc4.c | 2 +-
sound/soc/amd/acp3x-rt5682-max9836.c | 2 +-
sound/soc/atmel/sam9x5_wm8731.c | 2 +-
sound/soc/codecs/rt1318.c | 6 ++----
sound/soc/codecs/rt5514-spi.c | 2 +-
sound/soc/qcom/lpass-sc7280.c | 2 +-
sound/soc/samsung/aries_wm8994.c | 2 +-
I send everything else that I have to address the warnings, and
they are slowly making their way into the tree, as of today the
remaining ones are
drivers/char/apm-emulation.c | 5 ++---
drivers/char/tpm/tpm_ftpm_tee.c | 2 +-
drivers/comedi/drivers/ni_atmio.c | 2 +-
drivers/dma/img-mdc-dma.c | 2 +-
drivers/fpga/versal-fpga.c | 2 +-
drivers/input/touchscreen/stmpe-ts.c | 2 +-
drivers/mux/adg792a.c | 2 +-
drivers/net/ethernet/apm/xgene-v2/main.c | 4 +---
drivers/net/ethernet/hisilicon/hns_mdio.c | 2 +-
drivers/rtc/rtc-fsl-ftm-alarm.c | 2 +-
drivers/scsi/hisi_sas/hisi_sas_v1_hw.c | 2 +-
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 2 +-
drivers/tty/serial/amba-pl011.c | 6 +++---
drivers/tty/serial/ma35d1_serial.c | 2 +-
and I'm optimistic about most of them making it into the
next merge window. Once few enough are left, I can send
it again as a series that turns on the warning by default
and hopefully by that time we can wear down Mark enough
that he takes the patches even if he still disagrees ;-)
Arnd
next prev parent reply other threads:[~2025-02-27 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 10:08 Andy Shevchenko
2025-02-25 10:29 ` Arnd Bergmann
2025-02-25 10:37 ` Andy Shevchenko
2025-02-25 10:42 ` Arnd Bergmann
2025-02-25 10:48 ` Andy Shevchenko
2025-02-25 18:09 ` Arnd Bergmann
2025-02-25 17:21 ` Krzysztof Kozlowski
2025-02-26 14:18 ` Andy Shevchenko
2025-02-27 8:18 ` Arnd Bergmann [this message]
2025-03-03 11:07 ` Bartosz Golaszewski
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=f9b8acf8-7ed5-4d9f-84d1-acdbaa9e96d8@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®