mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Victor Lim <vlim@gigadevice.com>
Cc: tudor.ambarus@linaro.org, pratyush@kernel.org,
	miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
	akumarma@amd.com, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org, vikhyat.goyal@amd.com,
	Victor Lim <vlim@gigadevice.com>
Subject: Re: [PATCH V1 1/1] linux: drivers: mtd: spi-nor: gigadevice.c
Date: Thu, 20 Jul 2023 09:05:15 +0200	[thread overview]
Message-ID: <62663146a51c2beac4eff48abe1f61f8@walle.cc> (raw)
In-Reply-To: <20230720042834.12296-1-vlim@gigadevice.com>

Am 2023-07-20 06:28, schrieb Victor Lim:
> Adding gigedevice new part numbers
> 
> Signed-off-by: Victor Lim <vlim@gigadevice.com>

This is already v3 of this series. Please track and keep a change log.

Your previous ones were here:
https://lore.kernel.org/linux-mtd/20221204080000.4100-1-vlim@gigadevice.com/
https://lore.kernel.org/linux-mtd/20221206111037.8999-1-vlim@gigadevice.com/

> ---
>  drivers/mtd/spi-nor/gigadevice.c | 79 ++++++++++++++++++++++++++++++++
>  1 file changed, 79 insertions(+)
> 
> diff --git a/drivers/mtd/spi-nor/gigadevice.c 
> b/drivers/mtd/spi-nor/gigadevice.c
> index d57ddaf1525b..285fa42f2d97 100644
> --- a/drivers/mtd/spi-nor/gigadevice.c
> +++ b/drivers/mtd/spi-nor/gigadevice.c
> @@ -67,6 +67,85 @@ static const struct flash_info 
> gigadevice_nor_parts[] = {
>  		FLAGS(SPI_NOR_HAS_LOCK | SPI_NOR_HAS_TB | SPI_NOR_TB_SR_BIT6)
>  		FIXUP_FLAGS(SPI_NOR_4B_OPCODES)
>  		.fixups = &gd25q256_fixups },
> +/* adding these parts */

Why this comment?

> +	{ "gd25lx256e",  INFO(0xc86819, 0, 64 * 1024, 512,
> +			      SECT_4K | USE_FSR | SPI_NOR_OCTAL_READ |
> +			      SPI_NOR_4B_OPCODES | SPI_NOR_OCTAL_DTR_READ |
> +			      SPI_NOR_OCTAL_DTR_PP |
> +			      SPI_NOR_IO_MODE_EN_VOLATILE)
> +		.fixups = &gd25lx256e_fixups },
> +	{"gd25b512", INFO(0xc8471A, 0, 64 * 1024, 1024,	SECT_4K |
> +	SPI_NOR_QUAD_READ | SPI_NOR_HAS_LOCK | SPI_NOR_4B_OPCODES)},

Did you even compile this? INFO() doesn't take 5 arguments.
I'll stop here.

If you decide to post another version. Please read through all
the feedback you've got and esp. 
Documentation/process/submitting-patches.rst

Make it one patch per added part, don't include legacy flags if not 
needed,
include a test report and the dump of the SFDP tables.

Thanks,
-michael

  parent reply	other threads:[~2023-07-20  7:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20  4:28 Victor Lim
2023-07-20  6:25 ` kernel test robot
2023-07-20  6:53 ` Tudor Ambarus
2023-07-20  7:05 ` Michael Walle [this message]
     [not found]   ` <TY0PR06MB56580D3FEE55389F41E33398BB3EA@TY0PR06MB5658.apcprd06.prod.outlook.com>
2023-07-21  6:06     ` Tudor Ambarus
     [not found]       ` <TY0PR06MB56581B9A28DCD7A7270CFC0ABB3FA@TY0PR06MB5658.apcprd06.prod.outlook.com>
2023-07-21  7:38         ` Tudor Ambarus
2023-07-21  7:41           ` Michael Walle
2023-07-21  7:42             ` 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=62663146a51c2beac4eff48abe1f61f8@walle.cc \
    --to=michael@walle.cc \
    --cc=akumarma@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=tudor.ambarus@linaro.org \
    --cc=vigneshr@ti.com \
    --cc=vikhyat.goyal@amd.com \
    --cc=vlim@gigadevice.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

all inboxes | Powered by JetHome®