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]

Message-ID: <a5877032-ab30-a85d-cd42-93b75a84ab49@microchip.com>
Date:   Wed, 30 Jun 2021 18:28:16 +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 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?