linux-kernel - Re: [PATCH] spi: mt7621: allow GPIO chip select lines

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] [day] [month] [year] [list]

Message-ID: <92944d93690f8dbd1ad1008e5ceda854@risingedge.co.za>
Date: Sat, 16 Mar 2024 03:15:40 +0200
From: Justin Swartz <justin.swartz@...ingedge.co.za>
To: Mark Brown <broonie@...nel.org>
Cc: Matthias Brugger <matthias.bgg@...il.com>, AngeloGioacchino Del Regno
 <angelogioacchino.delregno@...labora.com>, linux-spi@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH] spi: mt7621: allow GPIO chip select lines

On 2024-03-16 03:11, Mark Brown wrote:
> On Sat, Mar 16, 2024 at 03:01:02AM +0200, Justin Swartz wrote:
> 
>> Please ignore this patch. It was accidentally sent without
>> "v2" nor --in-reply-to=...
> 
> The --in-reply-to should be avoided:
> 
> Please don't send new patches in reply to old patches or serieses, this
> makes it harder for both people and tools to understand what is going
> on - it can bury things in mailboxes and make it difficult to keep 
> track
> of what current patches are, both for the new patches and the old ones.

Thanks, I'll do that next time - already sent v2 in the wrong manner.