From: Ben Hutchings <ben@decadent.org.uk>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
MTD Maling List <linux-mtd@lists.infradead.org>,
Ian Campbell <ijc@hellion.org.uk>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Brian Norris <computersforpeace@gmail.com>,
Huang Shijie <shijie8@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
debian-kernel <debian-kernel@lists.debian.org>
Subject: Re: [PATCH v2 3/5] spi-nor: Make spi_nor_scan() take a chip type name, not an spi_device_id
Date: Tue, 30 Sep 2014 12:38:08 +0100 [thread overview]
Message-ID: <1412077088.9388.98.camel@decadent.org.uk> (raw)
In-Reply-To: <CACna6ryNp7+4y7oSs60atDZhUwFhiAyV4Oq5ELi1gyen45zhVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
On Tue, 2014-09-30 at 07:14 +0200, Rafał Miłecki wrote:
> On 30 September 2014 04:15, Ben Hutchings <ben@decadent.org.uk> wrote:
> > @@ -236,16 +236,13 @@ static int m25p_probe(struct spi_device *spi)
> > * If that's the case, respect "type" and ignore a "name".
> > */
> > if (data && data->type)
> > - id = spi_nor_match_id(data->type);
> > + name = data->type;
> >
> > /* If we didn't get name from platform, simply use "modalias". */
> > - if (!id) {
> > - id = spi_nor_match_id(spi_get_device_id(spi)->name);
> > - if (WARN_ON(!id))
> > - return -ENODEV;
> > - }
> > + if (!name)
> > + name = spi_get_device_id(spi)->name;
>
> Huh? Iterating the whole id_table, checking the entries (looking for
> one with name equal to the spi->modalias) and then... getting that
> name?
Ah, I didn't realise what spi_get_device_id() was doing.
> Did it hurt to use the patch I've sent
> mtd: m25p80: get rid of spi_get_device_id
> https://patchwork.ozlabs.org/patch/394328/
It would make sense to insert that before this.
Ben.
--
Ben Hutchings
The two most common things in the universe are hydrogen and stupidity.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2014-09-30 11:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 2:13 [PATCH v2 0/5] m25p80,spi-nor: Fix module aliases for m25p80; clean up chip identification Ben Hutchings
2014-09-30 2:14 ` [PATCH v2 1/5] m25p80,spi-nor: Fix module aliases for m25p80 Ben Hutchings
2014-10-10 4:51 ` Brian Norris
2014-10-17 16:23 ` Brian Norris
2014-10-17 16:35 ` Brian Norris
2014-10-17 16:41 ` Ben Hutchings
2014-09-30 2:15 ` [PATCH v2 2/5] spi-nor: Remove spi_nor::read_id operation Ben Hutchings
2014-10-22 8:30 ` Brian Norris
2014-09-30 2:15 ` [PATCH v2 3/5] spi-nor: Make spi_nor_scan() take a chip type name, not an spi_device_id Ben Hutchings
2014-09-30 5:14 ` Rafał Miłecki
2014-09-30 11:38 ` Ben Hutchings [this message]
2014-09-30 2:15 ` [PATCH v2 4/5] spi-nor: Replace struct spi_device_id with struct flash_info Ben Hutchings
2014-09-30 2:15 ` [PATCH v2 5/5] m25p80,spi-nor: Share the list of supported chip type names again Ben Hutchings
2014-09-30 7:22 ` Geert Uytterhoeven
2014-09-30 8:02 ` Rafał Miłecki
2014-09-30 11:36 ` Ben Hutchings
2014-10-10 4:55 ` 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=1412077088.9388.98.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=andrew@lunn.ch \
--cc=computersforpeace@gmail.com \
--cc=debian-kernel@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=ijc@hellion.org.uk \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=shijie8@gmail.com \
--cc=zajec5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox