public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	linux-mtd@lists.infradead.org, Kamal Dasu <kdasu.kdev@gmail.com>
Subject: Re: [PATCH] mtd: nand: Fix NAND_USE_BOUNCE_BUFFER flag conflict
Date: Tue, 7 Jul 2015 13:07:44 -0700	[thread overview]
Message-ID: <20150707200744.GG18370@brian-ubuntu> (raw)
In-Reply-To: <1435365838-10940-1-git-send-email-scottwood@freescale.com>

On Fri, Jun 26, 2015 at 07:43:58PM -0500, Scott Wood wrote:
> Commit 66507c7bc8895f0da6b ("mtd: nand: Add support to use nand_base
> poi databuf as bounce buffer") added a flag NAND_USE_BOUNCE_BUFFER
> using the same bit value as the existing NAND_BUSWIDTH_AUTO.

Good catch. It'd probably be easier to catch these things if we didn't
just manually type these in hex. Perhaps BIT() would make this more
obvious?

Anyway, looks good. Pushed to linux-mtd.git.

Brian

> Cc: Kamal Dasu <kdasu.kdev@gmail.com>
> Fixes: 66507c7bc8895f0da6b ("mtd: nand: Add support to use nand_base
> 	poi databuf as bounce buffer")
> Signed-off-by: Scott Wood <scottwood@freescale.com>
> ---
>  include/linux/mtd/nand.h | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/include/linux/mtd/nand.h b/include/linux/mtd/nand.h
> index 3d4ea7e..12b75f3 100644
> --- a/include/linux/mtd/nand.h
> +++ b/include/linux/mtd/nand.h
> @@ -176,17 +176,17 @@ typedef enum {
>  /* Chip may not exist, so silence any errors in scan */
>  #define NAND_SCAN_SILENT_NODEV	0x00040000
>  /*
> - * This option could be defined by controller drivers to protect against
> - * kmap'ed, vmalloc'ed highmem buffers being passed from upper layers
> - */
> -#define NAND_USE_BOUNCE_BUFFER	0x00080000
> -/*
>   * Autodetect nand buswidth with readid/onfi.
>   * This suppose the driver will configure the hardware in 8 bits mode
>   * when calling nand_scan_ident, and update its configuration
>   * before calling nand_scan_tail.
>   */
>  #define NAND_BUSWIDTH_AUTO      0x00080000
> +/*
> + * This option could be defined by controller drivers to protect against
> + * kmap'ed, vmalloc'ed highmem buffers being passed from upper layers
> + */
> +#define NAND_USE_BOUNCE_BUFFER	0x00100000
>  
>  /* Options set by nand scan */
>  /* Nand scan has allocated controller struct */
> -- 
> 2.1.4
> 

      reply	other threads:[~2015-07-07 20:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-27  0:43 [PATCH] mtd: nand: Fix NAND_USE_BOUNCE_BUFFER flag conflict Scott Wood
2015-07-07 20:07 ` Brian Norris [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=20150707200744.GG18370@brian-ubuntu \
    --to=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=kdasu.kdev@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=scottwood@freescale.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