[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a7ff3338-3d5e-4402-aaba-16e740f4ed5b@gmail.com>
Date: Wed, 1 Mar 2023 11:38:18 -0600
From: Ian Pilcher <arequipeno@...il.com>
To: Lee Jones <lee@...nel.org>
Cc: pavel@....cz, linux-leds@...r.kernel.org,
linux-kernel@...r.kernel.org, kabel@...nel.org
Subject: Re: [PATCH v13 0/2] Introduce block device LED trigger
On 3/1/23 08:27, Lee Jones wrote:
> Pavel,
>
> I see that you are active now - could you please prioritise this one.
>
Lee -
Just FYI, Pavel did respond. Unfortunately, he doesn't feel that this
can go in with its current sysfs interface, and making the change that
he wants would require changes to the block subsystem (adding an in-
kernel API to look up a block device by its kernel name, rather than its
major & minor numbers or a special file path).
Similar changes have been rejected in the past by the block subsystem
maintainers. The position I have seen is that major & minor numbers,
or device special files from which they can be determined, is *the*
interface to block devices.
I've also had some pretty negative experiences when interacting with the
block subsystem community - unnecessary profanity, etc.
Given that history, I don't see much prospect that I (an unknown newb)
would succeed in convincing the block subsystem maintainers to add the
API required to implement the interface that Pavel wants. So I'm pretty
much done trying to push this thing unless something changes that leads
me to think that there's actually a decent chance of success.
Hopefully that makes sense.
--
========================================================================
Google Where SkyNet meets Idiocracy
========================================================================
Powered by blists - more mailing lists