linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <oss@buserror.net>
To: Leo Li <pku.leo@gmail.com>, Raghav Dogra <raghav.dogra@nxp.com>
Cc: linux-mtd@lists.infradead.org,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	 Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>,
	Brian Norris <computersforpeace@gmail.com>,
	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: Thu, 18 Feb 2016 18:07:14 -0600	[thread overview]
Message-ID: <1455840434.2463.97.camel@buserror.net> (raw)
In-Reply-To: <CADRPPNS1i1XgtpyiT_=rDuDXBDn=ehNY32=RKTC9hdKXhWWq8A@mail.gmail.com>

On Thu, 2016-02-18 at 15:18 -0600, Leo Li wrote:
> On Wed, Feb 17, 2016 at 5:24 AM, Raghav Dogra <raghav.dogra@nxp.com> wrote:
> > The new IFC controller version 2.0 has a different memory map page.
> > Upto IFC 1.4 PAGE size is 4 KB and from IFC2.0 PAGE size is 64KB.
> > This patch segregates the IFC global and runtime registers to appropriate
> > PAGE sizes.
> > 
> > Signed-off-by: Jaiprakash Singh <b44839@freescale.com>
> > Signed-off-by: Raghav Dogra <raghav@freescale.com>
> > Acked-by: Li Yang <leoyang.li@nxp.com>
> > Signed-off-by: Raghav Dogra <raghav.dogra@nxp.com>
> > ---
> > Changes for v3: not dependent on
> > "drivers/memory: Add deep sleep support for IFC" patch
> > 
> > Changes for v2: rebased to resolve conflicts
> > Applicable to git://git.infradead.org/l2-mtd.git
> > 
> > This patch is dependent on "drivers/memory: Add deep sleep support for
> > IFC"
> > https://patchwork.ozlabs.org/patch/582762/
> > which is also applicable to git://git.infradead.org/l2-mtd.git
> 
> This patch seems to be in good shape, but the dependency is still
> having quite some feedback to be addressed.  Depending on it will
> greatly delay the time that this critical patch for LS2 to be merged.
> Could you remove the dependency like Scott already suggested?

According to the changelog the dependency has been removed (it would have been
clearer to remove this comment as well...).

-Scott

  reply	other threads:[~2016-02-19  0:07 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 [this message]
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

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=1455840434.2463.97.camel@buserror.net \
    --to=oss@buserror.net \
    --cc=b44839@freescale.com \
    --cc=computersforpeace@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --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).