From: Brian Norris <computersforpeace@gmail.com>
To: Huang Shijie <shijie.huang@intel.com>
Cc: devicetree@vger.kernel.org, Stefan Roese <sr@denx.de>,
Huang Shijie <shijie8@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: gpmi: Remove "We support only one NAND chip" from bindings doc
Date: Tue, 16 Dec 2014 17:17:57 -0800 [thread overview]
Message-ID: <20141217011757.GO9759@ld-irv-0074> (raw)
In-Reply-To: <20141203003542.GA7895@shldeISGChi005.sh.intel.com>
On Wed, Dec 03, 2014 at 08:35:42AM +0800, Huang Shijie wrote:
> On Tue, Dec 02, 2014 at 08:28:10AM +0100, Stefan Roese wrote:
> > On 02.12.2014 01:38, Huang Shijie wrote:
> > > On Mon, Dec 01, 2014 at 10:58:17AM +0100, Stefan Roese wrote:
> > >> On 30.11.2014 16:42, Huang Shijie wrote:
> > >>> On Sat, Nov 29, 2014 at 10:53:26PM -0800, Brian Norris wrote:
> > >>>> On Sat, Nov 29, 2014 at 10:40:50AM +0800, Huang Shijie wrote:
> > >>>>> On Fri, Nov 28, 2014 at 08:01:41AM +0100, Stefan Roese wrote:
> > >>>>>> On 28.11.2014 02:48, Huang Shijie wrote:
> > >>>>>>> On Thu, Nov 27, 2014 at 03:18:49PM +0100, Stefan Roese wrote:
> > >>>>>>>> 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
> > >>>>>>>
> > >>>>>>> The gpmi can only supports one chip. Of course, there are maybe two dies
> > >>>>>>> in this single chip.
[...]
> If your test result can prove that the gpmi can support two chips.
>
> I can ack this patch. (I ever thought the gpmi needs an extra patch to
> support the multiple chips)
>
> >
> > > I even did not have enough time to test the "two chips on a die" case very carefully before
> > > I left freescale.
> >
> > I see. Thanks for the hint. But this "two chips on a die" scenario did
> > pass some basic tests, no?
> yes. It passed the bonnie++ test.
If there are no more concrete objections, I'll apply this patch.
Brian
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2014-12-17 1:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 14:18 [PATCH] mtd: gpmi: Remove "We support only one NAND chip" from bindings doc Stefan Roese
[not found] ` <1417097929-17832-1-git-send-email-sr-ynQEQJNshbs@public.gmane.org>
2014-11-28 1:48 ` 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 [this message]
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=20141217011757.GO9759@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=shijie.huang@intel.com \
--cc=shijie8@gmail.com \
--cc=sr@denx.de \
/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