public inbox for kernelnewbies@kernelnewbies.org
 help / color / mirror / Atom feed
From: Torin Carey <torin@tcarey.uk>
To: Alison Schofield <alison.schofield@intel.com>
Cc: Kernel Newbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Existing patches of similar content
Date: Mon, 15 Sep 2025 12:41:06 +0000	[thread overview]
Message-ID: <aMgJWxFoqbpxJfyi@tcarey.uk> (raw)
In-Reply-To: <aL9PK7fTu12zceWC@aschofie-mobl2.lan>

On Mon, Sep 08, 2025 at 02:48:27PM -0700, Alison Schofield wrote:
> Kudo's to you for asking and for looking through the lore history of your
> subsystem and finding the history of this feature.
> 
> There's a lot of variability in lore mailing lists, reviewers, and maintainers
> responsiveness, so to be generic, I'll suggest your #2 option. Reply to the
> patch, show what you'd like to change, and see what happens.
> 
> Maybe you breathe new life into it, the original author picks up your changes,
> and the feature moves forward.
> 
> Maybe the original author acknowledges your changes and asks you to pick it up
> and carry it forward.
> 
> Maybe crickets, in which case you can submit a new patch, probably with a tag
> 'Originally-by:' or 'Co-developed-by'.
> 
> BTW if you do pick it up, make sure to address any concerns raised with the
> original patch.
> 
> Good Luck,
> Alison

Hi Alison,

Thanks for the advice!  In that case I'll work on putting some review comments
together and see if it goes anywhere.  If not I'll consider publishing my own
patch.

The original patch didn't seem to receive any concerns, but hopefully some
renewal to it could get some more attention on it.

Thanks,
Torin


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

      reply	other threads:[~2025-09-15 12:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07 18:57 Existing patches of similar content Torin Carey
2025-09-08 21:48 ` Alison Schofield
2025-09-15 12:41   ` Torin Carey [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=aMgJWxFoqbpxJfyi@tcarey.uk \
    --to=torin@tcarey.uk \
    --cc=alison.schofield@intel.com \
    --cc=kernelnewbies@kernelnewbies.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