netdev - Re: [PATCH] USB: zaurus: support another broken Zaurus

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: <118c84c8-d3aa-c3cb-06f4-c088e49c416f@suse.com>
Date:   Thu, 10 Feb 2022 15:20:38 +0100
From:   Oliver Neukum <oneukum@...e.com>
To:     Greg KH <gregkh@...uxfoundation.org>,
        Oliver Neukum <oneukum@...e.com>
CC:     bids.7405@...pond.com, linux-usb@...r.kernel.org,
        netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org
Subject: Re: [PATCH] USB: zaurus: support another broken Zaurus


On 10.02.22 15:17, Greg KH wrote:
> On Thu, Feb 10, 2022 at 03:13:49PM +0100, Oliver Neukum wrote:
>>
>>> And isn't there a needed "Reported-by:" for this one as it came from a
>>> bug report?
>> Do we do these for reports by the kernel.org bugzilla?
> We should, why not?

Hi,


because it sort of implies that it was reported to a mailing list.
If there is a bugzilla for it, shouldn't we reference it?

    Regards
        Oliver