linux-kernel - Re: [PATCH 00/52] USB: store owner from modules with usb_serial_register

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: <ee4daf22-8979-45f7-8e20-3cafd6c3e8f3@linaro.org>
Date: Fri, 3 May 2024 11:49:53 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Johan Hovold <johan@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/52] USB: store owner from modules with
 usb_serial_register_drivers()

On 15/04/2024 10:54, Johan Hovold wrote:
> On Thu, Mar 28, 2024 at 11:05:38PM +0100, Krzysztof Kozlowski wrote:
>> Merging
>> =======
>> All further patches depend on the first patch.
>>
>> Description
>> ===========
>> This is going to be a bit of a patch-bomb, but with trivial patches, so
>> I think it is still acceptable. If it is too much, apologies and I will
>> solve it.
> 
> No, sending 51 trivial one-line cleanup patches like this is not
> acceptable.
> 
> This is just one logical change so squash them all into one patch for
> the entire subsystem (i.e. this series should contain two patches).
> 

Sure. This is not exactly one logical change, but two, because the first
patch might fix some drivers which forgot to set the owner (even if I
did not identify them).

Best regards,
Krzysztof