From: <Tudor.Ambarus@microchip.com>
To: <michael@walle.cc>
Cc: <p.yadav@ti.com>, <miquel.raynal@bootlin.com>, <richard@nod.at>,
<vigneshr@ti.com>, <linux-mtd@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] mtd: spi-nor: winbond: use SNOR_ID3() for w25q512nwm
Date: Tue, 19 Jul 2022 07:24:17 +0000 [thread overview]
Message-ID: <0125cf8a-be06-e422-8e8f-157cf9dccb4c@microchip.com> (raw)
In-Reply-To: <4ac08f08010a71e288b0114fc02d47a4@walle.cc>
On 7/19/22 10:02, Michael Walle wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Am 2022-07-19 08:00, schrieb Tudor.Ambarus@microchip.com:
>> On 7/18/22 10:25, Michael Walle wrote:
>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know
>>> the content is safe
>>>
>>> Am 2022-07-12 10:40, schrieb Tudor.Ambarus@microchip.com:
>>>> Shaik, can we have your Tested-by tag on this?
>>>
>>> Sigh. His email address bounces with "The email address you
>>> entered couldn't be found." So don't expect a Tested-by: here.
>>>
>>
>> Would you drop this and pick the other patches that use your SNOR_ID3
>> and submit them all in a single patch set?
>
> I can collect the other patches, but why drop this if we know
> for a fact that the flash will work? (Because it is the same
> as the w25q512nwq)
>
Was it tested? I don't mind to queue it, but I thought we only queue
changes that were tested on actual hw.
next prev parent reply other threads:[~2022-07-19 7:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 14:02 [PATCH 0/2] introduce SNOR_ID3() Michael Walle
2022-05-10 14:02 ` [PATCH 1/2] mtd: spi-nor: " Michael Walle
2022-06-05 15:00 ` Tom Fitzhenry
2022-07-12 7:23 ` Pratyush Yadav
2022-07-15 12:19 ` Biju Das
2022-07-19 5:57 ` Tudor.Ambarus
2022-07-19 7:07 ` Michael Walle
2022-07-19 7:33 ` Tudor.Ambarus
2022-07-19 7:57 ` Michael Walle
2022-07-19 8:30 ` Tudor.Ambarus
2022-07-28 3:24 ` Tudor.Ambarus
2022-07-28 13:12 ` Michael Walle
2022-07-28 13:31 ` Tudor.Ambarus
2022-07-28 13:56 ` Michael Walle
2022-05-10 14:02 ` [PATCH 2/2] mtd: spi-nor: winbond: use SNOR_ID3() for w25q512nwm Michael Walle
2022-07-12 8:40 ` Tudor.Ambarus
2022-07-18 7:21 ` Michael Walle
2022-07-18 7:25 ` Michael Walle
2022-07-19 6:00 ` Tudor.Ambarus
2022-07-19 7:02 ` Michael Walle
2022-07-19 7:24 ` Tudor.Ambarus [this message]
2022-05-10 14:03 ` [PATCH 0/2] mtd: spi-nor: introduce SNOR_ID3() Michael Walle
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=0125cf8a-be06-e422-8e8f-157cf9dccb4c@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--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