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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Thu, 1 Jul 2021 05:25:51 +0000
From:   <Tudor.Ambarus@...rochip.com>
To:     <michael@...le.cc>
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

On 6/30/21 9:28 PM, Tudor.Ambarus@...rochip.com wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> 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

s/later/letter

> new flash addition is proposed?
Vendors shouldn't complain if we publish the SFDP data, since it can be freely read
from their flash products. I'll update the documentation and add this requirement for
new flash additions.