[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mafs0frkqyoph.fsf@kernel.org>
Date: Fri, 07 Feb 2025 11:32:58 +0000
From: Pratyush Yadav <pratyush@...nel.org>
To: Michael Walle <mwalle@...nel.org>
Cc: Cheng Ming Lin <linchengming884@...il.com>, tudor.ambarus@...aro.org,
pratyush@...nel.org, miquel.raynal@...tlin.com, richard@....at,
vigneshr@...com, linux-mtd@...ts.infradead.org,
linux-kernel@...r.kernel.org, alvinzhou@...c.com.tw, leoyu@...c.com.tw,
Cheng Ming Lin <chengminglin@...c.com.tw>
Subject: Re: [PATCH 2/2] mtd: spi-nor: macronix: Add support for Macronix
NOR Flash
On Fri, Feb 07 2025, Michael Walle wrote:
> Hi Cheng,
>
>> From: Cheng Ming Lin <chengminglin@...c.com.tw>
>> Due to incorrect values in the 4-BAIT table for these two flash IDs,
>> it is necessary to add these two flash IDs with fixups.
>
> What's the part number of these flashes?
>
>> --- a/drivers/mtd/spi-nor/macronix.c
>> +++ b/drivers/mtd/spi-nor/macronix.c
>> @@ -127,6 +127,9 @@ static const struct flash_info macronix_nor_parts[] = {
>> .size = SZ_128M,
>> .no_sfdp_flags = SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ,
>> .fixups = ¯onix_qpp4b_fixups,
>> + }, {
>
> Although we don't have .name anymore, a comment like
>
> /* <partname> */
>
> is recommended.
+1
I have been recommending this in other patches as well. Going through
commit messages can be tricky. This lets us still identify flash entries
easily. Let's recommend this for all patches going forward.
--
Regards,
Pratyush Yadav
Powered by blists - more mailing lists