[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0125cf8a-be06-e422-8e8f-157cf9dccb4c@microchip.com>
Date: Tue, 19 Jul 2022 07:24:17 +0000
From: <Tudor.Ambarus@...rochip.com>
To: <michael@...le.cc>
CC: <p.yadav@...com>, <miquel.raynal@...tlin.com>, <richard@....at>,
<vigneshr@...com>, <linux-mtd@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] mtd: spi-nor: winbond: use SNOR_ID3() for w25q512nwm
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@...rochip.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@...rochip.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.
Powered by blists - more mailing lists