From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>,
Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH 2/2] eeprom: 93xx46: drop unneeded MODULE_ALIAS
Date: Wed, 8 May 2024 21:17:59 +0200 [thread overview]
Message-ID: <cb8df682-c006-46d7-bcf1-7a0548e65c98@kernel.org> (raw)
In-Reply-To: <5b29d981-aa8a-413e-8250-5fb33802f32d@app.fastmail.com>
On 08/05/2024 21:11, Arnd Bergmann wrote:
> On Wed, May 8, 2024, at 20:44, Krzysztof Kozlowski wrote:
>> On 08/05/2024 20:28, Andy Shevchenko wrote:
>>> On Wed, May 08, 2024 at 08:15:00PM +0200, Krzysztof Kozlowski wrote:
>>>> On 08/05/2024 19:53, Andy Shevchenko wrote:
>>>>> On Sun, Apr 14, 2024 at 05:49:57PM +0200, Krzysztof Kozlowski wrote:
>>>>>> The ID table already has respective entry and MODULE_DEVICE_TABLE and
>>>>>> creates proper alias for SPI driver. Having another MODULE_ALIAS causes
>>>>>> the alias to be duplicated.
>>>
>>> ...
>>>
>>>>>> MODULE_ALIAS("spi:93xx46");
>>>>>
>>>>> I was stumbled over this (leftover?).
>>>>> Commit message doesn't elaborate this bit.
>>>>> Any comments?
>>>>
>>>> It is not present in ID table and commit msg removes only duplicated
>>>> aliases. That alias has meaning - someone might be actually relying on it.
>>>
>>> It seems no users for it. The only user of platform data of this EEPROM uses
>>> board files which AFAIU bypasses modalias matching.
>>
>> I don't think that's correct. The modalias of SPI board is there on
>> purpose.
>
> Right, but I think a better workaround would have been to change
> the board_info to pick a modalias that is part of the ID table:
>
> --- a/drivers/misc/eeprom/digsy_mtc_eeprom.c
> +++ b/drivers/misc/eeprom/digsy_mtc_eeprom.c
> @@ -76,7 +76,7 @@ static struct gpiod_lookup_table eeprom_spi_gpiod_table = {
>
> static struct spi_board_info digsy_mtc_eeprom_info[] __initdata = {
> {
> - .modalias = "93xx46",
> + .modalias = "eeprom-93xx46",
> .max_speed_hz = 1000000,
> .bus_num = EE_SPI_BUS_NUM,
> .chip_select = 0,
>
That's kind of independent change. This commit *only* removed duplicated
aliases, thus should have not functional impact except dropping
redundant code. What you propose is to change spi board matching, which
is reasonable, just a different thing.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-05-08 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 15:49 [PATCH 1/2] eeprom: at25: drop unneeded MODULE_ALIAS Krzysztof Kozlowski
2024-04-14 15:49 ` [PATCH] mtd: mchp23k256: " Krzysztof Kozlowski
2024-04-14 15:49 ` [PATCH 2/2] eeprom: 93xx46: " Krzysztof Kozlowski
2024-05-08 17:53 ` Andy Shevchenko
2024-05-08 18:15 ` Krzysztof Kozlowski
2024-05-08 18:28 ` Andy Shevchenko
2024-05-08 18:44 ` Krzysztof Kozlowski
2024-05-08 19:11 ` Arnd Bergmann
2024-05-08 19:17 ` Krzysztof Kozlowski [this message]
2024-05-10 14:28 ` 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=cb8df682-c006-46d7-bcf1-7a0548e65c98@kernel.org \
--to=krzk@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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