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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 30 Mar 2022 11:19:53 +0300
From:   Kalle Valo <>
To:     Jeff Johnson <>
Cc:     Benjamin St├╝rz <>,
        <>, <>,
        <>, <>,
        <>, <>,
        <>, <>
Subject: Re: [PATCH 19/22 v2] wcn36xx: Improve readability of wcn36xx_caps_name

Kalle Valo <> writes:

> Jeff Johnson <> writes:
>> (apologies for top-posting)
>> When you submit new patches you should not do so as a reply, but
>> instead as a new thread with a new version number.
>> And since multiple folks have suggested that you submit on a
>> per-subsystem basis I suggest that you re-send this as a singleton
>> just to and
>> along with the associated maintainers.
>> So I believe [PATCH v3] wcn36xx:... would be the correct subject, but
>> I'm sure Kalle will let us know otherwise
> You are correct. Also I strongly recommend using git send-email instead
> of Mozilla. Patch handling is automated using patchwork and git, so
> submitting patches manually is error prone.

Yeah, our patchwork didn't even detect this patch. But v3 is visible and
is on my queue:


Powered by blists - more mailing lists