From: <Tudor.Ambarus@microchip.com>
To: <vigneshr@ti.com>, <liu.xiang6@zte.com.cn>,
<linux-mtd@lists.infradead.org>
Cc: richard@nod.at, liuxiang_1999@126.com,
linux-kernel@vger.kernel.org, marek.vasut@gmail.com,
miquel.raynal@bootlin.com, computersforpeace@gmail.com,
dwmw2@infradead.org
Subject: Re: [PATCH v4] mtd: spi-nor: fix nor->addr_width when its value configured from SFDP does not match the actual width
Date: Fri, 28 Jun 2019 08:20:54 +0000 [thread overview]
Message-ID: <32340066-402a-0067-8694-91e34e7a7480@microchip.com> (raw)
In-Reply-To: <792b5942-9aca-b0f2-dd92-cb8f96cd8027@ti.com>
On 06/27/2019 04:23 PM, Vignesh Raghavendra wrote:
> External E-Mail
>
>
>
> On 24/06/19 9:30 PM, Liu Xiang wrote:
>> IS25LP256 gets BFPT_DWORD1_ADDRESS_BYTES_3_ONLY from BFPT table for
>> address width. But in actual fact the flash can support 4-byte address.
>> Use a post bfpt fixup hook to overwrite the address width advertised by
>> the BFPT.
>>
>> Suggested-by: Tudor Ambarus <tudor.ambarus@microchip.com>
dropped Suggested-by tag, you can't add this tag for each change request. You
should add it only when someone gives you the general idea on how to do the patch.
>> Signed-off-by: Liu Xiang <liu.xiang6@zte.com.cn>
>>
>
> Reviewed-by: Vignesh Raghavendra <vigneshr@ti.com>
>
> Regards
> Vignesh
>
>> ---
>>
>> Changes in v4:
>> update the comment suggested by Tudor.
>> ---
>> drivers/mtd/spi-nor/spi-nor.c | 25 ++++++++++++++++++++++++-
>> 1 file changed, 24 insertions(+), 1 deletion(-)
>>
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git,
spi-nor/next branch.
Thanks,
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2019-06-28 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 16:00 [PATCH v4] mtd: spi-nor: fix nor->addr_width when its value configured from SFDP does not match the actual width Liu Xiang
2019-06-27 13:23 ` Vignesh Raghavendra
2019-06-28 8:20 ` Tudor.Ambarus [this message]
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=32340066-402a-0067-8694-91e34e7a7480@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=liu.xiang6@zte.com.cn \
--cc=liuxiang_1999@126.com \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.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;
as well as URLs for NNTP newsgroup(s).