From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Roger Knecht <roger@norberthealth.com>,
linux-kernel@vger.kernel.org, Ivo van Doorn <IvDoorn@gmail.com>,
kernel-janitors@vger.kernel.org, linux-doc@vger.kernel.org,
Kristian Hoegsberg <krh@redhat.com>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
akpm@linux-foundation.org
Subject: Re: [PATCH v5] crc-itu-t: Fix typo in CRC ITU-T polynom comment
Date: Thu, 2 Jun 2022 19:16:55 +0200 [thread overview]
Message-ID: <Ypjwh5f6ByoZl5YE@zx2c4.com> (raw)
In-Reply-To: <47a68855-4547-49dd-d7eb-8ef83630552c@infradead.org>
Hi Randy,
On Thu, Jun 02, 2022 at 09:31:24AM -0700, Randy Dunlap wrote:
>
>
> On 6/2/22 07:24, Roger Knecht wrote:
> > On Sat, May 21, 2022 at 5:44 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> >> I don't know which maintainer will merge this since no one is Cc:ed on it.
> >> You will probably need to choose some maintainer to send the patch to.
> >>
> >> But let's add the people who merged the header file in the first place
> >> for their comments/review. (done)
> >
> > Thanks Randy.
> >
> > The CRC implementation seems to be unmaintained (no entry in the
> > MAINTAINER file).
> > Any idea which maintainer I can send the patch to?
>
> Yes, the 2 people who signed off on its merger are not active AFAICT.
>
> > The kernel doc mentions Andrew Morton as last resort (added to CC):
> >> You should always copy the appropriate subsystem maintainer(s) on any patch to
> >> code that they maintain; look through the MAINTAINERS file and the source code
> >> revision history to see who those maintainers are. The script scripts/get_maintainer.pl
> >> can be very useful at this step. If you cannot find a maintainer for the subsystem you
> >> are working on, Andrew Morton (akpm@linux-foundation.org) serves as a maintainer
> >> of last resort.
> > source: https://www.kernel.org/doc/html/latest/process/submitting-patches.html
>
> Yes, Andrew can merge it.
> Or possibly Jason (also Cc-ed).
Sure, I can take this.
Jason
>
> thanks.
>
> --
> ~Randy
next prev parent reply other threads:[~2022-06-02 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 12:47 [PATCH v5] crc-itu-t: Fix typo in CRC ITU-T polynom comment Roger Knecht
2022-05-21 15:44 ` Randy Dunlap
2022-06-02 14:24 ` Roger Knecht
2022-06-02 16:31 ` Randy Dunlap
2022-06-02 17:16 ` Jason A. Donenfeld [this message]
2022-06-03 8:20 ` Roger Knecht
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=Ypjwh5f6ByoZl5YE@zx2c4.com \
--to=jason@zx2c4.com \
--cc=IvDoorn@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=krh@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=roger@norberthealth.com \
--cc=stefanr@s5r6.in-berlin.de \
/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