Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date:   Thu, 01 Jul 2021 08:15:35 +0200
From:   Michael Walle <michael@walle.cc>
To:     Tudor.Ambarus@microchip.com
Cc:     code@reto-schneider.ch, linux-mtd@lists.infradead.org, sr@denx.de,
        reto.schneider@husqvarnagroup.com, miquel.raynal@bootlin.com,
        p.yadav@ti.com, richard@nod.at, vigneshr@ti.com,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] mtd: spi-nor: Add support for XM25QH64C
In-Reply-To: <a5877032-ab30-a85d-cd42-93b75a84ab49@microchip.com>
References: <20210613121248.1529292-1-code@reto-schneider.ch>
 <1ba367f93650cb65122acd32fb4a4159@walle.cc>
 <0328347c-572d-b636-5542-99cb36e9efa9@microchip.com>
 <064317e561f1ad20282efe778f633723@walle.cc>
 <a5877032-ab30-a85d-cd42-93b75a84ab49@microchip.com>
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <3b2184a8c637e89ffba3013bbee0393a@walle.cc>
Precedence: bulk

Am 2021-06-30 20:28, schrieb Tudor.Ambarus@microchip.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