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] [day] [month] [year] [list]
Date:   Wed, 8 Mar 2023 10:34:35 -0800
From:   Grant Grundler <grundler@...omium.org>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Grant Grundler <grundler@...omium.org>,
        Oleksij Rempel <linux@...pel-privat.de>,
        Pavel Skripkin <paskripkin@...il.com>,
        Lukas Wunner <lukas@...ner.de>,
        Eizan Miyamoto <eizan@...omium.org>,
        netdev <netdev@...r.kernel.org>,
        "David S . Miller" <davem@...emloft.net>,
        LKML <linux-kernel@...r.kernel.org>,
        Anton Lundin <glance@....umu.se>
Subject: Re: [PATCHv2 1/2] TEST:net: asix: fix modprobe "sysfs: cannot create
 duplicate filename"

On Tue, Mar 7, 2023 at 4:47 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Tue,  7 Mar 2023 12:05:01 -0800 Grant Grundler wrote:
> > Subject: [PATCHv2 1/2] TEST:net: asix: fix modprobe "sysfs: cannot create duplicate filename"
>
> Why the "TEST:" prefix?

Sorry - that's left over from how I mark the change for testing with
chromeos-5.15 kernel branch:
   https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/4313619

I should have removed that.  I upload the change to gerrit so partners
can easily test the same code  (e.g. coworker Eizan who is in
Australia).

If you follow the link above, you can see I'm testing a bunch of
additional backports as well and have additional fields in the commit
message required by chromium.org.

> The patch doesn't apply cleanly, it needs to go via this tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/
> so rebase it onto that, please, and put [PATCH net] in the subject
> rather than just [PATCH].

Ok - thanks! Wil repost v3 against netdev/net.git/ shortly. No problem.

> Keep patch 2 locally for about a week (we merge fixes and cleanup
> branches once a week around Thu, and the two patches depend on each
> other).

Awesome! Sounds good.

> Please look thru at least the tl;dr of our doc:
> https://www.kernel.org/doc/html/next/process/maintainer-netdev.html

Thanks!

Because I've been "randomly" contributing to netdev for 20+ years,
I've not looked for documentation (beyond SubmittingPatches). But I am
quite willing to read and follow it - makes life easier for everyone.

cheers,
grant

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ