devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: linux-mtd@lists.infradead.org
Cc: devicetree@vger.kernel.org,
	Brian Norris <computersforpeace@gmail.com>,
	Huang Shijie <b32955@freescale.com>
Subject: [PATCH] mtd: gpmi: Remove "We support only one NAND chip" from bindings doc
Date: Thu, 27 Nov 2014 15:18:49 +0100	[thread overview]
Message-ID: <1417097929-17832-1-git-send-email-sr@denx.de> (raw)

This sentence "We support only one NAND chip now" is not true any more.
Multiple chips are supported. So lets remove this sentence to not
confuse anyone.

Signed-off-by: Stefan Roese <sr@denx.de>
Cc: Huang Shijie <b32955@freescale.com>
Cc: Brian Norris <computersforpeace@gmail.com>
---
 Documentation/devicetree/bindings/mtd/gpmi-nand.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/mtd/gpmi-nand.txt b/Documentation/devicetree/bindings/mtd/gpmi-nand.txt
index a011fdf..d02acaf 100644
--- a/Documentation/devicetree/bindings/mtd/gpmi-nand.txt
+++ b/Documentation/devicetree/bindings/mtd/gpmi-nand.txt
@@ -1,7 +1,7 @@
 * Freescale General-Purpose Media Interface (GPMI)
 
 The GPMI nand controller provides an interface to control the
-NAND flash chips. We support only one NAND chip now.
+NAND flash chips.
 
 Required properties:
   - compatible : should be "fsl,<chip>-gpmi-nand"
-- 
2.2.0


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

             reply	other threads:[~2014-11-27 14:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27 14:18 Stefan Roese [this message]
     [not found] ` <1417097929-17832-1-git-send-email-sr-ynQEQJNshbs@public.gmane.org>
2014-11-28  1:48   ` [PATCH] mtd: gpmi: Remove "We support only one NAND chip" from bindings doc Huang Shijie
     [not found]     ` <20141128014832.GA3113-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2014-11-28  7:01       ` Stefan Roese
     [not found]         ` <54781DD5.5030801-ynQEQJNshbs@public.gmane.org>
2014-11-29  2:40           ` Huang Shijie
     [not found]             ` <20141129024047.GA5056-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2014-11-30  6:53               ` Brian Norris
2014-11-30 15:42                 ` Huang Shijie
     [not found]                   ` <20141130154255.GB14834-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2014-12-01  9:58                     ` Stefan Roese
     [not found]                       ` <547C3BB9.1010706-ynQEQJNshbs@public.gmane.org>
2014-12-02  0:38                         ` Huang Shijie
     [not found]                           ` <20141202003840.GA11370-eV5aV+vWts7EmYkesOTNgGFmcEqAMTzPQQ4Iyu8u01E@public.gmane.org>
2014-12-02  7:28                             ` Stefan Roese
     [not found]                               ` <547D6A0A.70409-ynQEQJNshbs@public.gmane.org>
2014-12-03  0:35                                 ` Huang Shijie
2014-12-17  1:17                                   ` Brian Norris
2014-12-18  2:45                                     ` Brian Norris

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=1417097929-17832-1-git-send-email-sr@denx.de \
    --to=sr@denx.de \
    --cc=b32955@freescale.com \
    --cc=computersforpeace@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.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).