From: Brian Norris <computersforpeace@gmail.com>
To: Li Yang <leoli@freescale.com>
Cc: Raghav Dogra <raghav@freescale.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
oss@buserror.net, prabhakar.kushwaha@nxp.com,
Jaiprakash Singh <b44839@freescale.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 3/3] mtd/ifc: Segregate IFC fcm and runtime registers
Date: Mon, 1 Feb 2016 12:43:39 -0800 [thread overview]
Message-ID: <20160201204339.GK19540@google.com> (raw)
In-Reply-To: <CADRPPNThvUNOtN=2PErWVfhKz_xqBmps+HyL8GTo8+D_-eKX4Q@mail.gmail.com>
On Mon, Feb 01, 2016 at 01:41:45PM -0600, Li Yang wrote:
> On Mon, Feb 1, 2016 at 4:46 AM, Raghav Dogra <raghav@freescale.com> wrote:
>
> A general comment is that you should include the linux-mtd mailing
> list and it's maintainers for this set of patches. Although the
> MAINTAINERS file doesn't specify a maintainer for drivers/memory
> directory, it should be most related to linux-mtd, IMO.
Yes, please resend.
This is especially odd, considering that it appears your resending here
is in direct response to my comments on the linux-mtd mailing list, and
neither I nor linux-mtd were CC'd on this iteration...
> > IFC has two set of registers viz FCM (Flash control machine)
> > aka global and run time registers. These set are defined in two
> > memory map PAGES. Upto IFC 1.4 PAGE size is 4 KB and from IFC2.0
> > PAGE size is 64KB
>
> So I guess this patch is the critical change to make the fsl_ifc
> driver work with the version 2.0 hardware block? If so, it will be
> better to mention this in the patch title.
I made a similar comment on the 1st version. But I can't see the patch
this time :(
> > Signed-off-by: Jaiprakash Singh <b44839@freescale.com>
> > Signed-off-by: Raghav Dogra <raghav@freescale.com>
> > ---
> > drivers/memory/fsl_ifc.c | 251 +++++++++++++++++++++-------------------
> > drivers/mtd/nand/fsl_ifc_nand.c | 72 ++++++------
> > include/linux/fsl_ifc.h | 48 +++++---
> > 3 files changed, 203 insertions(+), 168 deletions(-)
Brian
next prev parent reply other threads:[~2016-02-01 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 10:46 [PATCH 1/3] driver/memory: Removal of deprecated NO_IRQ Raghav Dogra
2016-02-01 10:46 ` [PATCH 2/3] driver/memory: Update dependency of IFC for Layerscape Raghav Dogra
2016-05-16 0:21 ` [2/3] " Scott Wood
2016-02-01 10:46 ` [PATCH 3/3] mtd/ifc: Segregate IFC fcm and runtime registers Raghav Dogra
2016-02-01 19:41 ` Li Yang
2016-02-01 20:43 ` Brian Norris [this message]
2016-02-01 22:26 ` Scott Wood
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=20160201204339.GK19540@google.com \
--to=computersforpeace@gmail.com \
--cc=b44839@freescale.com \
--cc=dwmw2@infradead.org \
--cc=leoli@freescale.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oss@buserror.net \
--cc=prabhakar.kushwaha@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).