lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ypjwh5f6ByoZl5YE@zx2c4.com>
Date:   Thu, 2 Jun 2022 19:16:55 +0200
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     Roger Knecht <roger@...berthealth.com>,
        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

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@...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?
> 
> 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@...ux-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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ