From: Brian Norris <computersforpeace@gmail.com>
To: Raghav Dogra <raghav.dogra@nxp.com>
Cc: Leo Li <pku.leo@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Yang-Leo Li <leoyang.li@nxp.com>,
Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>,
Scott Wood <oss@buserror.net>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Raghav Dogra <raghav@freescale.com>,
Jaiprakash Singh <b44839@freescale.com>
Subject: Re: [PATCH][v3] mtd/ifc: Add support for IFC controller version 2.0
Date: Wed, 29 Jun 2016 10:32:23 -0700 [thread overview]
Message-ID: <20160629173223.GA47625@google.com> (raw)
In-Reply-To: <DB4PR04MB346C1FA9FCC3906B906E7C589230@DB4PR04MB346.eurprd04.prod.outlook.com>
Hi,
On Wed, Jun 29, 2016 at 02:53:03PM +0000, Raghav Dogra wrote:
>
>
> > -----Original Message-----
> > From: Leo Li [mailto:pku.leo@gmail.com]
> > Sent: Saturday, May 28, 2016 3:34 AM
1 month delay? So much for the rush...
> > To: Brian Norris <computersforpeace@gmail.com>; Raghav Dogra
> > <raghav.dogra@nxp.com>
> > Cc: Boris Brezillon <boris.brezillon@free-electrons.com>; Yang-Leo Li
> > <leoyang.li@nxp.com>; Prabhakar Kushwaha
> > <prabhakar.kushwaha@nxp.com>; Scott Wood <oss@buserror.net>; linux-
> > mtd@lists.infradead.org; linuxppc-dev <linuxppc-dev@lists.ozlabs.org>;
> > Raghav Dogra <raghav@freescale.com>; Jaiprakash Singh
> > <b44839@freescale.com>
> > Subject: Re: [PATCH][v3] mtd/ifc: Add support for IFC controller version 2.0
> >
> > On Fri, May 27, 2016 at 4:12 PM, Brian Norris
> > <computersforpeace@gmail.com> wrote:
> > > On Fri, May 27, 2016 at 10:44:01PM +0200, Boris Brezillon wrote:
> > >> On Fri, 27 May 2016 15:15:00 -0500
> > >> Leo Li <pku.leo@gmail.com> wrote:
> > >> >
> > >> > The pull request does have patch "mtd/ifc: Add support for IFC
> > >> > controller version 2.0", but it doesn't have another patch
> > >> > "driver/memory: Update dependency of IFC for
> > >> > Layerscape"(https://patchwork.ozlabs.org/patch/557389/) needed to
> > >> > make the driver selectable on new hardware.
> > >
[...]
> > >> BTW, in the patch description you say you're only modifying a Kconfig
> > >> dependency, but you're actually doing more than that: you're removing
> > >> an asm header inclusion and manually include several other headers
> > >> (which I guess were previously included by asm/prom.h).
> > >
> > > Please resend this patch with a more complete commit description; I'd
> > > like it to get actual review (and time in linux-next) before it gets
> > > merged, so at best, it'll wait a few -rc's. I also suspect the patch
> > > isn't optimal. I believe Scott has suggested [1] that we didn't need
> > > the FSL_SOC dependency on the LBC driver. I think IFC looks like a
> > > similar case?
>
> Hi Brian,
>
> The patch being talked about does not add a FSL_SOC dependency on the IFC driver.
> It uses a generic ARCH_LAYERSCAPE macro to enable IFC. This should be Ok?
Maybe... but if we know that this driver doesn't actually have an
FSL_SOC dependency, and the FSL maintainers don't really want it in the
first place, then a simpler patch is to just remove the FSL_SOC
dependency, rather than making the deps more complicated.
But anyway, if you resend with the comments addresses (e.g., better
commit description), then we can consider applying it. If the FSL folks
have nothing to contribute here, then I don't see why we wouldn't take
your patch.
Regards,
Brian
prev parent reply other threads:[~2016-06-29 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 11:24 [PATCH][v3] mtd/ifc: Add support for IFC controller version 2.0 Raghav Dogra
2016-02-17 21:49 ` Scott Wood
2016-02-18 21:18 ` Leo Li
2016-02-19 0:07 ` Scott Wood
2016-03-30 20:43 ` Li Yang
2016-04-06 17:52 ` Brian Norris
2016-04-06 18:53 ` Yang-Leo Li
2016-04-08 0:45 ` Boris Brezillon
2016-05-25 19:18 ` Leo Li
2016-05-25 20:34 ` Boris Brezillon
2016-05-27 20:15 ` Leo Li
2016-05-27 20:44 ` Boris Brezillon
2016-05-27 21:12 ` Brian Norris
2016-05-27 21:16 ` Boris Brezillon
2016-05-27 22:03 ` Leo Li
2016-06-29 14:53 ` Raghav Dogra
2016-06-29 17:32 ` 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=20160629173223.GA47625@google.com \
--to=computersforpeace@gmail.com \
--cc=b44839@freescale.com \
--cc=boris.brezillon@free-electrons.com \
--cc=leoyang.li@nxp.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oss@buserror.net \
--cc=pku.leo@gmail.com \
--cc=prabhakar.kushwaha@nxp.com \
--cc=raghav.dogra@nxp.com \
--cc=raghav@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;
as well as URLs for NNTP newsgroup(s).