From: "B48286@freescale.com" <B48286@freescale.com>
To: 'Brian Norris' <computersforpeace@gmail.com>
Cc: Scott Wood <scottwood@freescale.com>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"Mingkai.Hu@freescale.com" <Mingkai.Hu@freescale.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Subject: RE: [PATCH] mtd: m25p80: Make the name of mtd_info fixed
Date: Thu, 23 Jan 2014 03:29:41 +0000 [thread overview]
Message-ID: <66941b677b7e4b8d9ce4cc44304b0955@DM2PR03MB301.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20140123021213.GZ8919@ld-irv-0074>
Hi Brian,
Thanks for your comments!
> -----Original Message-----
> From: Brian Norris [mailto:computersforpeace@gmail.com]
> Sent: Thursday, January 23, 2014 10:12 AM
> To: Hou Zhiqiang-B48286
> Cc: linux-mtd@lists.infradead.org; linuxppc-dev@ozlabs.org; Wood Scott-
> B07421; Hu Mingkai-B21284; Ezequiel Garcia
> Subject: Re: [PATCH] mtd: m25p80: Make the name of mtd_info fixed
>
> Hi Hou,
>
> On Mon, Jan 06, 2014 at 02:34:29PM +0800, Hou Zhiqiang wrote:
> > To give spi flash layout using "mtdparts=..." in cmdline, we must give
> > mtd_info a fixed name,because the cmdlinepart's parser will match the
> > name given in cmdline with the mtd_info.
> >
> > Now, if use OF node, mtd_info's name will be spi->dev->name. It
> > consists of spi_master->bus_num, and the spi_master->bus_num maybe
> > dynamically fetched.
> > So, give the mtd_info a new fiexd name "name.cs", "name" is name of
> > spi_device_id and "cs" is chip-select in spi_dev.
> >
> > Signed-off-by: Hou Zhiqiang <b48286@freescale.com>
> > ---
> > drivers/mtd/devices/m25p80.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/mtd/devices/m25p80.c
> > b/drivers/mtd/devices/m25p80.c index eb558e8..d1ed480 100644
> > --- a/drivers/mtd/devices/m25p80.c
> > +++ b/drivers/mtd/devices/m25p80.c
> > @@ -1012,7 +1012,8 @@ static int m25p_probe(struct spi_device *spi)
> > if (data && data->name)
> > flash->mtd.name = data->name;
> > else
> > - flash->mtd.name = dev_name(&spi->dev);
> > + flash->mtd.name = kasprintf(GFP_KERNEL, "%s.%d",
> > + id->name, spi->chip_select);
>
> Changing the mtd.name may have far-reaching consequences for users who
> already have mtdparts= command lines. But your concern is probably valid
> for dynamically-determined bus numbers. Perhaps you can edit this patch
> to only change the name when the busnum is dynamically-allocated?
>
It's a good idea, but in the case of mtd_info's name dynamically-allocated
using "mtdparts=..." in command lines is illegal obviously. Would you tell
me what side-effect will be brought by the change of mtd_info's name.
Thanks
> This also needs a NULL check (for OOM), and you leak memory on device
> removal.
>
Yes, it's necessary to check the return value of function kasprintf.
> >
> > flash->mtd.type = MTD_NORFLASH;
> > flash->mtd.writesize = 1;
>
> Brian
>
Thanks,
Hou Zhiqiang
next prev parent reply other threads:[~2014-01-23 3:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 6:34 [PATCH] mtd: m25p80: Make the name of mtd_info fixed Hou Zhiqiang
2014-01-23 2:12 ` Brian Norris
2014-01-23 3:29 ` B48286 [this message]
2014-02-10 18:47 ` 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=66941b677b7e4b8d9ce4cc44304b0955@DM2PR03MB301.namprd03.prod.outlook.com \
--to=b48286@freescale.com \
--cc=Mingkai.Hu@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@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