[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aSl7sWjt6fqgirvI@MNI-190>
Date: Fri, 28 Nov 2025 11:38:41 +0100
From: Jose Javier Rodriguez Barbarin <dev-josejavier.rodriguez@...gon.com>
To: Andy Shevchenko <andy.shevchenko@...il.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 06:12:29PM +0200, Andy Shevchenko wrote:
> 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.
>
Understood. This was my first patch that touches more than one subsystem
and I was doubting to send one unique patch or one patch per driver.
Good to know that.
Thank you so much.
>
> --
> With Best Regards,
> Andy Shevchenko
Powered by blists - more mailing lists