[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y/ZVOfaApSo/Dslf@sirena.org.uk>
Date: Wed, 22 Feb 2023 17:47:37 +0000
From: Mark Brown <broonie@...nel.org>
To: Saravana Kannan <saravanak@...gle.com>
Cc: Liam Girdwood <lgirdwood@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Bjorn Andersson <andersson@...nel.org>,
Sudeep Holla <sudeep.holla@....com>,
Tony Lindgren <tony@...mide.com>,
Doug Anderson <dianders@...omium.org>,
Guenter Roeck <linux@...ck-us.net>,
Luca Weiss <luca.weiss@...rphone.com>, kernel-team@...roid.com,
linux-kernel@...r.kernel.org
Subject: Re: [RFC v1 2/4] regulator: core: Add sysfs class backward
compatibility
On Sat, Feb 18, 2023 at 12:32:49AM -0800, Saravana Kannan wrote:
> A regulator device's sysfs directory used to be created under
> /sys/class/regulator when it is added to a class. Since the device is
> now moved to be under a bus, add symlinks from /sys/class/regulator to
> the real device sysfs directory.
Shouldn't this be squashed into the previous patch given that it creates
a bisection issue?
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists