From: jim.cromie@gmail.com
To: Ian Pilcher <arequipeno@gmail.com>
Cc: Greg KH <greg@kroah.com>,
linux-modules@vger.kernel.org,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Seeking advice on "monkey patching" a driver
Date: Thu, 1 Jul 2021 15:04:28 -0600 [thread overview]
Message-ID: <CAJfuBxwoFGh9ei=_GEe4V8f7vMtH-G-pdOy4CvQKi-2nHeBQ8g@mail.gmail.com> (raw)
In-Reply-To: <b6e41740-94b7-e32e-5d57-deb7b730b2d9@gmail.com>
On Thu, Jul 1, 2021 at 2:03 PM Ian Pilcher <arequipeno@gmail.com> wrote:
>
> On 7/1/21 12:59 PM, Greg KH wrote:
> > Oh that's horrible, please no, do not do that :)
>
> Indeed it is, but it works, and it meets my main objective, which is to
> allow the use of distribution kernel packages and modules.
>
> > How about a third option, the correct one:
> > - submit your code changes upstream and they get merged into the
> > main kernel tree and no monkeypatching is ever needed at all!
> >
> > Have you submitted your changes upstream to the existing drivers? What
> > is preventing that from happening today?
>
> There are a couple of reasons that I've never attempted to do this.
>
> * Scope of work - Currently, there is simply no mechanism to call an LED
> * (Probable) lack of upstream interest - As I mentioned, disk activity
> LEDs really ought to be handled by the hardware.
Are LEDs really that important?
Unless theyre rigged intrinsically into the operation, it seems tertiary
I don't know of any
> other system that suffers from this particular limitation. So this
> is a very, very niche use case. (Most users of this hardware use the
> manufacturer's "firmware".)
>
> I did ask about this on the linux-ide mailing list long ago when I
> first wrote the modules, but I don't think that I ever received a
> response, which reinforces my belief that upstream isn't likely to be
> receptive.
>
theres a firehose of patches.
FWIW, now robots watch the list, and will grind your patches on lots
of configs. arches
> I've invested significant time in kernel patches in the past, only to
> see them ultimately not be accepted, so I would need to know that
> upstream was truly interested in such a feature before I would consider
> making such a commitment.
>
no guarantees, but there is staging. (here, more or less)
provisional home for code while quality develops
once youre in-tree, warts and all (to some extent, I dont know)
you may well get help (patches) improving it, surely lots of feedback.
elsewhere, nobody knows it exists.
next prev parent reply other threads:[~2021-07-01 21:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 16:25 Seeking advice on "monkey patching" a driver Ian Pilcher
2021-07-01 17:59 ` Greg KH
2021-07-01 20:03 ` Ian Pilcher
2021-07-01 21:04 ` jim.cromie [this message]
2021-07-02 4:31 ` Greg KH
2021-07-02 12:05 ` Ian Pilcher
2021-07-02 12:20 ` Greg KH
2021-07-02 15:16 ` Ian Pilcher
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='CAJfuBxwoFGh9ei=_GEe4V8f7vMtH-G-pdOy4CvQKi-2nHeBQ8g@mail.gmail.com' \
--to=jim.cromie@gmail.com \
--cc=arequipeno@gmail.com \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-modules@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).