linux-kernel - Re: [PATCH 1/2] xhci: Introduce "disable-usb3" DT property/quirk

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: <bceffb44-037a-487f-87d2-15f1b3a4f9ed@kernel.org>
Date:   Sun, 10 Dec 2023 12:10:22 +0100
From:   Krzysztof Kozlowski <krzk@...nel.org>
To:     Sam Edwards <cfsworks@...il.com>,
        Mathias Nyman <mathias.nyman@...el.com>,
        Thinh Nguyen <Thinh.Nguyen@...opsys.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Heiko Stuebner <heiko@...ech.de>, linux-usb@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] xhci: Introduce "disable-usb3" DT property/quirk

On 09/12/2023 20:26, Sam Edwards wrote:
>> Performing review on untested code might be
>> a waste of time, thus I will skip this patch entirely till you follow
>> the process allowing the patch to be tested.
> 
> That's fine; this patch has just failed review anyway (due to the new 
> property not being introduced in a separate patch), and I'll need to 
> prepare and send a v2 to proceed. However as I mentioned in the cover, 
> this is a semi-RFC. I haven't discussed the overall idea with anyone 
> yet, so to avoid wasting my own time, I need to give the USB folks ample 

It does not really explain why you did not Cc some of the maintainers.
If this is a RFC, even though not marked as such in subject prefix, then
I guess all maintainers should be involved for comments.

Best regards,
Krzysztof