linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Huang Shijie <b32955@freescale.com>,
	Lee Jones <lee.jones@linaro.org>,
	linux-mtd@lists.infradead.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH 1/9] mtd: spi-nor: drop \t after #define
Date: Wed, 9 Apr 2014 19:40:14 +0200	[thread overview]
Message-ID: <201404091940.14392.marex@denx.de> (raw)
In-Reply-To: <1397064774-31784-1-git-send-email-computersforpeace@gmail.com>

On Wednesday, April 09, 2014 at 07:32:46 PM, Brian Norris wrote:
> Spacing is a little non-standard here.
> 
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
> ---
> Series based on l2-mtd.git/spinor:
> 
>   http://git.infradead.org/l2-mtd.git
> 
>  include/linux/mtd/spi-nor.h | 68
> ++++++++++++++++++++++----------------------- 1 file changed, 34
> insertions(+), 34 deletions(-)
> 
> diff --git a/include/linux/mtd/spi-nor.h b/include/linux/mtd/spi-nor.h
> index 41dae78fbd1d..558097e14932 100644
> --- a/include/linux/mtd/spi-nor.h
> +++ b/include/linux/mtd/spi-nor.h
> @@ -2,50 +2,50 @@
>  #define __LINUX_MTD_SPI_NOR_H
> 
>  /* Flash opcodes. */
> -#define	OPCODE_WREN		0x06	/* Write enable */
> -#define	OPCODE_RDSR		0x05	/* Read status register */
> -#define	OPCODE_WRSR		0x01	/* Write status register 1 byte 
*/
> -#define	OPCODE_NORM_READ	0x03	/* Read data bytes (low 
frequency) */
> -#define	OPCODE_FAST_READ	0x0b	/* Read data bytes (high 
frequency) */
> -#define	OPCODE_DUAL_READ        0x3b    /* Read data bytes (Dual SPI) */
> -#define	OPCODE_QUAD_READ        0x6b    /* Read data bytes (Quad SPI) */
> -#define	OPCODE_PP		0x02	/* Page program (up to 256 
bytes) */
> -#define	OPCODE_BE_4K		0x20	/* Erase 4KiB block */
> -#define	OPCODE_BE_4K_PMC	0xd7	/* Erase 4KiB block on PMC chips 
*/
> -#define	OPCODE_BE_32K		0x52	/* Erase 32KiB block */
> -#define	OPCODE_CHIP_ERASE	0xc7	/* Erase whole flash chip */
> -#define	OPCODE_SE		0xd8	/* Sector erase (usually 64KiB) 
*/
> -#define	OPCODE_RDID		0x9f	/* Read JEDEC ID */
> -#define	OPCODE_RDCR             0x35    /* Read configuration register 
*/
> +#define OPCODE_WREN		0x06	/* Write enable */
> +#define OPCODE_RDSR		0x05	/* Read status register */
> +#define OPCODE_WRSR		0x01	/* Write status register 1 byte */
> +#define OPCODE_NORM_READ	0x03	/* Read data bytes (low frequency) */
> +#define OPCODE_FAST_READ	0x0b	/* Read data bytes (high frequency) */
> +#define OPCODE_DUAL_READ        0x3b    /* Read data bytes (Dual SPI) */
> +#define OPCODE_QUAD_READ        0x6b    /* Read data bytes (Quad SPI) */

This is still a little non-standard -- or rather -- inconsistent here. You 
should use space after #define and \t after the name I'd say. I'd also say these 
two slipped your attention as the others do it just like that.

> +#define OPCODE_PP		0x02	/* Page program (up to 256 bytes) */
> +#define OPCODE_BE_4K		0x20	/* Erase 4KiB block */
> +#define OPCODE_BE_4K_PMC	0xd7	/* Erase 4KiB block on PMC chips */
> +#define OPCODE_BE_32K		0x52	/* Erase 32KiB block */
> +#define OPCODE_CHIP_ERASE	0xc7	/* Erase whole flash chip */
> +#define OPCODE_SE		0xd8	/* Sector erase (usually 64KiB) */
> +#define OPCODE_RDID		0x9f	/* Read JEDEC ID */
> +#define OPCODE_RDCR             0x35    /* Read configuration register */

DTTO here.

>  /* 4-byte address opcodes - used on Spansion and some Macronix flashes. */
> -#define	OPCODE_NORM_READ_4B	0x13	/* Read data bytes (low 
frequency) */
> -#define	OPCODE_FAST_READ_4B	0x0c	/* Read data bytes (high 
frequency) */
> -#define	OPCODE_DUAL_READ_4B	0x3c    /* Read data bytes (Dual SPI) */
> -#define	OPCODE_QUAD_READ_4B	0x6c    /* Read data bytes (Quad SPI) */
> -#define	OPCODE_PP_4B		0x12	/* Page program (up to 256 
bytes) */
> -#define	OPCODE_SE_4B		0xdc	/* Sector erase (usually 64KiB) 
*/
> +#define OPCODE_NORM_READ_4B	0x13	/* Read data bytes (low frequency) */
> +#define OPCODE_FAST_READ_4B	0x0c	/* Read data bytes (high frequency) */
> +#define OPCODE_DUAL_READ_4B	0x3c    /* Read data bytes (Dual SPI) */
> +#define OPCODE_QUAD_READ_4B	0x6c    /* Read data bytes (Quad SPI) */

This comment here is indented with spaces, while the other comments are indented 
with tabs ;-/
[...]

  parent reply	other threads:[~2014-04-09 17:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09 17:32 [PATCH 1/9] mtd: spi-nor: drop \t after #define Brian Norris
2014-04-09 17:32 ` [PATCH 2/9] mtd: spi-nor: re-name OPCODE_* to SPINOR_OP_* Brian Norris
2014-04-09 17:41   ` Marek Vasut
2014-04-10  7:42   ` Huang Shijie
2014-04-09 17:32 ` [PATCH 3/9] mtd: spi-nor: unify read opcode variants with ST SPI FSM Brian Norris
2014-04-09 17:41   ` Marek Vasut
2014-04-10  7:43   ` Huang Shijie
2014-04-10  7:47   ` Huang Shijie
2014-04-10 19:34     ` Brian Norris
2014-04-09 17:32 ` [PATCH 4/9] Documentation: spi-nor: rewrite some portions Brian Norris
2014-04-09 17:44   ` Marek Vasut
2014-04-09 18:14     ` Brian Norris
2014-04-09 17:32 ` [PATCH 5/9] mtd: spi-nor: shorten Kconfig naming Brian Norris
2014-04-09 17:44   ` Marek Vasut
2014-04-10  7:39   ` Huang Shijie
2014-04-09 17:32 ` [PATCH 6/9] mtd: st_spi_fsm: fixup Kconfig dependency Brian Norris
2014-04-10  7:57   ` Lee Jones
2014-04-09 17:32 ` [PATCH 7/9] mtd: st_spi_fsm: kill duplicate CMD definitions Brian Norris
2014-04-10  7:56   ` Lee Jones
2014-04-10 18:58     ` Brian Norris
2014-04-10 18:01   ` Geert Uytterhoeven
2014-04-10 18:59     ` Brian Norris
2014-04-09 17:32 ` [PATCH 8/9] mtd: st_spi_fsm: replace FLACH_CMD_* with SPINOR_OP_* Brian Norris
2014-04-10  7:52   ` Lee Jones
2014-04-09 17:32 ` [PATCH 9/9] mtd: st_spi_fsm: begin using spi-nor.h opcodes Brian Norris
2014-04-10  7:50   ` Lee Jones
2014-04-09 17:40 ` Marek Vasut [this message]
2014-04-09 17:56   ` [PATCH 1/9] mtd: spi-nor: drop \t after #define Brian Norris
2014-04-10  7:34 ` Huang Shijie

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=201404091940.14392.marex@denx.de \
    --to=marex@denx.de \
    --cc=b32955@freescale.com \
    --cc=computersforpeace@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    /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).