From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] mtd: nand: Update dependency of IFC for LS1021A
Date: Mon, 6 Feb 2017 10:05:42 +0100 [thread overview]
Message-ID: <20170206100542.65f19dc5@bbrezillon> (raw)
In-Reply-To: <DB6PR0401MB2584DBE5D6496F44B7169B49F4600@DB6PR0401MB2584.eurprd04.prod.outlook.com>
Hi Alison,
On Thu, 5 Jan 2017 02:02:30 +0000
Alison Wang <alison.wang@nxp.com> wrote:
> > On 01/04/2017 02:46 AM, Alison Wang wrote:
> > >> On 01/03/2017 03:41 AM, Alison Wang wrote:
> > >>> As NAND support for Freescale/NXP IFC controller is available on
> > >>> LS1021A, the dependency for LS1021A is added.
> > >>
> > >> Does LS stand for LayerScape ? Yes it does. So why does
> > >> ARCH_LAYERSCAPE not cover LS1021 ?
> > > [Alison Wang] LS1021A is an earlier product and is not compatible
> > with later Layerscape architecture. So ARCH_LAYERSCAPE can't cover
> > LS1021A.
> >
> > Ah ok, I see. That information would be useful in the commit message ;-)
> >
> [Alison Wang] Ok. :)
Would you mind sending a v3 with the updated commit message?
Thanks,
Boris
next prev parent reply other threads:[~2017-02-06 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 2:41 [PATCH v2 1/2] mtd: ifc: Update dependency of IFC for LS1021A Alison Wang
2017-01-03 2:41 ` [PATCH v2 2/2] mtd: nand: " Alison Wang
2017-01-03 11:46 ` Marek Vasut
2017-01-04 1:46 ` Alison Wang
2017-01-04 1:50 ` Marek Vasut
2017-01-05 2:02 ` Alison Wang
2017-02-06 9:05 ` Boris Brezillon [this message]
2017-02-13 6:59 ` Alison Wang
2017-01-03 9:04 ` [PATCH v2 1/2] mtd: ifc: " Boris Brezillon
2017-01-03 9:19 ` Alison Wang
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=20170206100542.65f19dc5@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@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).