public inbox for kernelnewbies@kernelnewbies.org
 help / color / mirror / Atom feed
From: Ian Pilcher <arequipeno@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: linux-modules@vger.kernel.org, kernelnewbies@kernelnewbies.org
Subject: Re: Seeking advice on "monkey patching" a driver
Date: Fri, 2 Jul 2021 10:16:44 -0500	[thread overview]
Message-ID: <f524169d-4f5c-bd05-3190-b2544887cca1@gmail.com> (raw)
In-Reply-To: <YN8EecLokJuHrptR@kroah.com>

On 7/2/21 7:20 AM, Greg KH wrote:
> Again, without a real patch, no maintainer or developer will ever say if
> they will, or will not, accept such a thing.  That's just not how kernel
> development works.  Working patches are what is discussed as that proves
> that at least, the idea works.

And that's certainly their prerogative.  You asked why I hadn't
attempted to submit changes upstream to address my issue, and I provided
my reasons for not doing so.

After several experiences where I've invested a significant (to me)
amount of time, only to ultimately be told that the functionality that I
implemented really wasn't desired, I'm very reluctant to repeat that
experience (and I honestly don't think that's particularly selfish or
unreasonable).

This doesn't mean that I absolutely won't make an attempt to do this.
As I mentioned in my previous note, the existence of ledtrig-disk.c
gives me some hope that changes might be accepted.

I'll just have to see ...

-- 
========================================================================
                  In Soviet Russia, Google searches you!
========================================================================

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2021-07-02 15:17 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
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 [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=f524169d-4f5c-bd05-3190-b2544887cca1@gmail.com \
    --to=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