linux-kernel - Re: [PATCH v1] mtd: spi-nor: Add support for XM25QH64C

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 01 Jul 2021 08:15:35 +0200
From:   Michael Walle <michael@...le.cc>
To:     Tudor.Ambarus@...rochip.com
Cc:     code@...o-schneider.ch, linux-mtd@...ts.infradead.org, sr@...x.de,
        reto.schneider@...qvarnagroup.com, miquel.raynal@...tlin.com,
        p.yadav@...com, richard@....at, vigneshr@...com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] mtd: spi-nor: Add support for XM25QH64C

Am 2021-06-30 20:28, schrieb Tudor.Ambarus@...rochip.com:
> On 6/30/21 5:15 PM, Michael Walle wrote:
>>> 
>>> Can the SFDP dump fit in the commit message when introducing a new
>>> flash ID?
>> 
>> As ASCII hex dump? I'd guess we need some instructions how to do
>> that. 4k would be 256 lines with 16 byte per line.
>> 
>> But yes, I had the same thought.
> 
> How about asking for the SFDP data in the cover later each time a
> new flash addition is proposed?

Ahh, I like the idea to put it onto the ML only. What do you think
of putting it into the comment section of the patch (ie. the one
after "---". This way we can have a backreference with a Link:
tag of the patch.

-michael