[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfhM5GuYY1qUKgBhePDo4oe5k3K1ZDTPbYJNr5NtjVVfQ@mail.gmail.com>
Date: Thu, 27 Nov 2025 18:12:29 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Jose Javier Rodriguez Barbarin <dev-josejavier.rodriguez@...gon.com>
Cc: linus.walleij@...aro.org, brgl@...nel.org, jic23@...nel.org,
dlechner@...libre.com, nuno.sa@...log.com, andy@...nel.org,
gregkh@...uxfoundation.org, jirislaby@...nel.org, morbidrsa@...il.com,
jth@...nel.org, wim@...ux-watchdog.org, linux@...ck-us.net, nathan@...nel.org,
nsc@...nel.org, linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-iio@...r.kernel.org, linux-serial@...r.kernel.org,
linux-watchdog@...r.kernel.org, linux-kbuild@...r.kernel.org,
Jorge Sanjuan Garcia <dev-jorge.sanjuangarcia@...gon.com>
Subject: Re: [PATCH 2/2] mcb: Remove MODULE_ALIAS from all mcb client drivers
On Thu, Nov 27, 2025 at 5:56 PM Jose Javier Rodriguez Barbarin
<dev-josejavier.rodriguez@...gon.com> wrote:
>
> MODULE_ALIAS information is no longer needed as now all mcb client
> drivers are reporting such information through MODULE_DEVICE_TABLE.
While this is not a big change, I still would recommend to split on
per-driver basis, and with pushing the first one as kinda a fix after
v6.19-rc1 (to v6.19-rcX) allows other maintainers to apply the rest on
driver-basis. This helps everybody I assume.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists