[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKXUXMw+1a9ptkViye9sTKv8TwgGq72tBC6QR0FYRpXr942JEA@mail.gmail.com>
Date: Tue, 14 Mar 2023 09:14:30 +0100
From: Lukas Bulwahn <lukas.bulwahn@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Mark Brown <broonie@...nel.org>, Jens Axboe <axboe@...nel.dk>,
linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] spi: docs: adjust summary to CONFIG_SYSFS_DEPRECATED removal
On Tue, Mar 14, 2023 at 9:03 AM Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
>
> On Tue, Mar 14, 2023 at 08:56:09AM +0100, Lukas Bulwahn wrote:
> > With commit 721da5cee9d4 ("driver core: remove CONFIG_SYSFS_DEPRECATED and
> > CONFIG_SYSFS_DEPRECATED_V2"), ./scripts/checkkconfigsymbols.py indicated
> > an unresolved reference to the config SYSFS_DEPRECATED in the SPI summary
> > documentation.
> >
> > Simply, delete the sentence referring to the removed config there. Also
> > update the documentation, as these sys/class entries should always be
> > symlinks, as the commit message of the commit above suggests.
> >
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@...il.com>
> > ---
> > Mark, Greg, Jens, please confirm that these sys/class entries now always
> > are symlinks. That is simply my guess after reading a bit on sysfs_deprecated
> > also changed compared to the normal setup, but I am not the expert here.
>
> They have been symlinks for years, the only subsystem that the
> CONFIG_SYSFS_DEPRECATED logic still modified was for the block
> subsystem. So your change looks good to me, thanks for doing this:
>
Thanks for confirming, Greg. That was my wild guess and it was just a
quick update while passing through that one section of that whole
document.
Lukas
> Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>
Powered by blists - more mailing lists