public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Ian Pilcher <arequipeno@gmail.com>
Cc: pavel@ucw.cz, linux-leds@vger.kernel.org,
	linux-kernel@vger.kernel.org, kabel@kernel.org
Subject: Re: [PATCH v13 0/2] Introduce block device LED trigger
Date: Thu, 2 Mar 2023 16:04:26 +0000	[thread overview]
Message-ID: <ZADJCmMSCSuWFavm@google.com> (raw)
In-Reply-To: <a7ff3338-3d5e-4402-aaba-16e740f4ed5b@gmail.com>

On Wed, 01 Mar 2023, Ian Pilcher wrote:

> 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.

I understand and empathise with the situation.

Pavel is the boss here, so I cannot over-rule the decisions he makes.
Hopefully the two of you can find some middle ground and work something
out between you.  Best of luck.

-- 
Lee Jones [李琼斯]

      reply	other threads:[~2023-03-02 16:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27 22:52 [PATCH v13 0/2] Introduce block device LED trigger Ian Pilcher
2022-12-27 22:52 ` [PATCH v13 1/2] docs: Add block device (blkdev) LED trigger documentation Ian Pilcher
2023-01-09 18:05   ` Pavel Machek
2022-12-27 22:52 ` [PATCH v13 2/2] leds: trigger: Add block device LED trigger Ian Pilcher
2023-01-09 16:38 ` [PATCH v13 0/2] Introduce " Lee Jones
2023-03-01 14:27 ` Lee Jones
2023-03-01 17:38   ` Ian Pilcher
2023-03-02 16:04     ` Lee Jones [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZADJCmMSCSuWFavm@google.com \
    --to=lee@kernel.org \
    --cc=arequipeno@gmail.com \
    --cc=kabel@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox