[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAO_iFwrHcSWJm17fL-Q83DZ5i1xr+_dkEjh5Yt3Hxso0VtnzZw@mail.gmail.com>
Date: Thu, 2 Jun 2022 16:24:12 +0200
From: Roger Knecht <roger@...berthealth.com>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: linux-kernel@...r.kernel.org, Ivo van Doorn <IvDoorn@...il.com>,
kernel-janitors@...r.kernel.org, linux-doc@...r.kernel.org,
Kristian Hoegsberg <krh@...hat.com>,
Stefan Richter <stefanr@...6.in-berlin.de>,
akpm@...ux-foundation.org
Subject: Re: [PATCH v5] crc-itu-t: Fix typo in CRC ITU-T polynom comment
On Sat, May 21, 2022 at 5:44 PM Randy Dunlap <rdunlap@...radead.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?
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@...ux-foundation.org) serves as a maintainer
> of last resort.
source: https://www.kernel.org/doc/html/latest/process/submitting-patches.html
Roger
Powered by blists - more mailing lists