All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Leo Li <pku.leo@gmail.com>, Yang-Leo Li <leoyang.li@nxp.com>,
	Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>,
	Scott Wood <oss@buserror.net>,
	Raghav Dogra <raghav.dogra@nxp.com>,
	"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: Fri, 27 May 2016 14:12:47 -0700	[thread overview]
Message-ID: <20160527211247.GA123214@google.com> (raw)
In-Reply-To: <20160527224401.4b776ad4@bbrezillon>

Hi Leo,

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:
> > On Wed, May 25, 2016 at 3:34 PM, Boris Brezillon
> > <boris.brezillon@free-electrons.com> wrote:
> > > On Wed, 25 May 2016 14:18:43 -0500
> > > Leo Li <pku.leo@gmail.com> wrote:
> > >> It seems that the patch at https://patchwork.ozlabs.org/patch/557389/
> > >> mentioned above was not in tree for 4.7.  Can you review and apply
> > >> that patch too?  
> > >
> > > I see it in the PR Brian sent 2 days ago [1], so it should appear in
> > > Linus tree soon.
> > >
> > > Regards,
> > >
> > > Boris
> > >
> > > [1]https://lkml.org/lkml/2016/5/24/9  
> > 
> > 
> > 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.

Your patches seem to have broken threading. Or at least, in my mailbox,
I have that patch, but I can't easily find [PATCH 1/3] or [PATCH 3/3].
Please fix your threading next time, to help ensure things get handled
together.

(It also helps when you reply to the patch you're asking about, and not
to a different patch.)

> Sorry, I overlooked that part in your different emails (even though you
> clearly stated that you needed both patches).
> 
> For my defense, I haven't followed the patch series from the beginning,
> and only took the patch because Brian suggested to do so (and the
> changes seemed ok).
> It would have been clearer if the different patches were part of the
> same series.

+1 to the last sentence.

> Anyway, Brian, can you take it into your tree and make it appear in
> -rc1 (or earlier if it's still possible)?

Not sure how I could get it any "earlier"? It's not making -rc1 at this
point.

> 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?

Brian

[1] http://lists.infradead.org/pipermail/linux-mtd/2016-January/064855.html

  reply	other threads:[~2016-05-27 21:13 UTC|newest]

Thread overview: 19+ 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-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 [this message]
2016-05-27 21:16                       ` Boris Brezillon
2016-05-27 22:03                       ` Leo Li
2016-06-29 14:53                         ` Raghav Dogra
2016-06-29 14:53                           ` Raghav Dogra
2016-06-29 17:32                           ` 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=20160527211247.GA123214@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.