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
Date: Thu, 01 Jul 2021 08:15:35 +0200 [thread overview]
Message-ID: <3b2184a8c637e89ffba3013bbee0393a@walle.cc> (raw)
In-Reply-To: <a5877032-ab30-a85d-cd42-93b75a84ab49@microchip.com>
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
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-07-01 6:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 12:12 [PATCH v1] mtd: spi-nor: Add support for XM25QH64C Reto Schneider
2021-06-14 6:56 ` Michael Walle
2021-06-17 11:59 ` Reto Schneider
2021-06-17 14:19 ` Michael Walle
2021-06-17 15:06 ` Reto Schneider
2021-06-28 5:17 ` Tudor.Ambarus
2021-06-28 4:55 ` Tudor.Ambarus
2021-06-30 14:15 ` Michael Walle
2021-06-30 18:28 ` Tudor.Ambarus
2021-07-01 5:25 ` Tudor.Ambarus
2021-07-01 6:15 ` Michael Walle [this message]
2021-06-28 5:32 ` Tudor.Ambarus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3b2184a8c637e89ffba3013bbee0393a@walle.cc \
--to=michael@walle.cc \
--cc=Tudor.Ambarus@microchip.com \
--cc=code@reto-schneider.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=reto.schneider@husqvarnagroup.com \
--cc=richard@nod.at \
--cc=sr@denx.de \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox