linux-kernel - Re: [greybus-dev] Re: [PATCH linux-next] staging: greybus:using the

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: <a42bb5d5-4783-b755-5479-48c5bcdbbedd@linaro.org>
Date:   Wed, 3 Aug 2022 07:34:49 -0500
From:   Alex Elder <elder@...aro.org>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     cgel.zte@...il.com, linux-kernel@...r.kernel.org,
        greybus-dev@...ts.linaro.org, ye xingchen <ye.xingchen@....com.cn>,
        Zeal Robot <zealci@....com.cn>
Subject: Re: [greybus-dev] Re: [PATCH linux-next] staging: greybus:using the

On 8/3/22 7:30 AM, Greg KH wrote:
>>
>> Ye Xingchen had nothing to do with your receiving the message twice.
> Ah, ok.  But they did send a number of patches like this while after I
> had sent my first request to not do patches in this format anymore,
> which is what caused my response here.

I didn't realize that.  That explains why your response was
"Please follow researcher-guidelines.rst."  I didn't initially
understand why it was that instead of something more directed
at the content of the patch.

I *thought* it might be because "Zeal Robot" might be something
new, and so considered experimental?

Anyway, I think we're clear now.  Thanks.

					-Alex