From: Huang Shijie <shijie.huang@intel.com>
To: "Frank.Li@freescale.com" <Frank.Li@freescale.com>
Cc: "Fabio.Estevam@freescale.com" <Fabio.Estevam@freescale.com>,
Huang Shijie <shijie8@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"han.xu@freescale.com" <han.xu@freescale.com>,
Brian Norris <computersforpeace@gmail.com>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH v3 2/2] mtd: fsl-quadspi: Fix module unbound
Date: Wed, 14 Jan 2015 09:04:20 +0800 [thread overview]
Message-ID: <20150114010419.GA10784@hsj.sh.intel.com> (raw)
In-Reply-To: <BY1PR0301MB12213C4577DB849CA161F51482400@BY1PR0301MB1221.namprd03.prod.outlook.com>
On Tue, Jan 13, 2015 at 10:05:29PM +0000, Frank.Li@freescale.com wrote:
>
> > Hi Fabio,
> >
> > On Tue, Jan 13, 2015 at 07:45:22PM -0200, Fabio Estevam wrote:
> > > On Tue, Jan 13, 2015 at 4:51 PM, Brian Norris
> > > <computersforpeace@gmail.com> wrote:
> > >
> > > >> - Read the two flashes.
> > > >
> > > > Are you doing any verification to make sure you're reading the
> > > > *correct* data? I'd imagine from some what I see in your patches,
> > > > that you might actually be reading from the wrong flash.
> > >
> > > Yes, you are right. Just confirmed that with this v3 applied I erased
> > > /dev/mtd0, but that also incorrectly erased /dev/mtd1.
> > >
> > > Now I came back to the original v1 patch: isn't it the simpler
> > > approach for fixing the module load/unload crash problem?
> > >
> > > It only keeps the mtd unregistration index in sync with registration
> > > and doesn't touch other areas of the driver.
> > >
> > > IMHO it is an improvement over the current situation.
> >
> > Right, I thought your original patch was an improvement, but it did still leave
> > some of the error path broken. And as Huang mentioned, multiple devices
> > were never actually *properly* supported, so there were problems there.
> >
> > > I agree that this driver needs more rework, but I am not able to put
> > > it on such good state.
> >
> > I might be OK with taking v1 if we can do the following:
> >
> > (1) Identify who will take responsibility for testing and improving this driver.
> > We might even add a MAINTAINERS entry
>
> Our QSPI driver owner Xu han (han.xu@freescale.com) will take responsibility to test and improve
> This driver. I will help him to be familiar with linux kernel community work.
Good news.
Huang Shijie
next prev parent reply other threads:[~2015-01-14 1:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 10:32 [PATCH v3 1/2] mtd: fsl-quadspi: Call fsl_qspi_set_base_addr after nor_size is set Fabio Estevam
2015-01-07 10:32 ` [PATCH v3 2/2] mtd: fsl-quadspi: Fix module unbound Fabio Estevam
2015-01-09 20:17 ` Brian Norris
2015-01-13 15:35 ` Fabio Estevam
2015-01-13 18:51 ` Brian Norris
2015-01-13 21:45 ` Fabio Estevam
2015-01-13 21:58 ` Brian Norris
2015-01-13 22:04 ` Fabio Estevam
2015-01-13 22:05 ` Frank.Li
2015-01-14 1:04 ` Huang Shijie [this message]
2015-01-14 20:26 ` Fabio Estevam
2015-01-14 22:53 ` Brian Norris
2015-01-15 15:46 ` Han Xu
2015-01-15 16:34 ` Han Xu
2015-01-15 16:45 ` Fabio Estevam
2015-01-09 20:26 ` [PATCH v3 1/2] mtd: fsl-quadspi: Call fsl_qspi_set_base_addr after nor_size is set Brian Norris
2015-01-12 1:48 ` Huang Shijie
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=20150114010419.GA10784@hsj.sh.intel.com \
--to=shijie.huang@intel.com \
--cc=Fabio.Estevam@freescale.com \
--cc=Frank.Li@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=festevam@gmail.com \
--cc=han.xu@freescale.com \
--cc=linux-mtd@lists.infradead.org \
--cc=shijie8@gmail.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.