From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: Potential namespace problem for 'struct flash_platfrom_data'
Date: Thu, 29 Apr 2010 16:47:36 -0600 [thread overview]
Message-ID: <n2nfa686aa41004291547wb6a1c67bq4d4c7140cb3fcddc@mail.gmail.com> (raw)
In-Reply-To: <0D753D10438DA54287A00B0270842697636E30604F@AUSP01VMBX24.collaborationhost.net>
On Thu, Apr 29, 2010 at 2:35 PM, H Hartley Sweeten
<hartleys@visionengravers.com> wrote:
> On Thursday, April 29, 2010 1:20 PM, Russell King wrote:
>> On Thu, Apr 29, 2010 at 03:06:37PM -0500, H Hartley Sweeten wrote:
>>> Hello all,
>>>
>>> I was looking at an issue with a spi flash device and noticed a
>>> potential namespace problem.
>>>
>>> arch/arm/include/asm/mach/flash.h has this:
>>>
>>> struct flash_platform_data {
>>> ? ? ?const char ? ? ?*map_name;
>>> ? ? ?const char ? ? ?*name;
>>> ? ? ?unsigned int ? ?width;
>>> ? ? ?int ? ? ? ? ? ? (*init)(void);
>>> ? ? ?void ? ? ? ? ? ?(*exit)(void);
>>> ? ? ?void ? ? ? ? ? ?(*set_vpp)(int on);
>>> ? ? ?void ? ? ? ? ? ?(*mmcontrol)(struct mtd_info *mtd, int sync_read);
>>> ? ? ?struct mtd_partition *parts;
>>> ? ? ?unsigned int ? ?nr_parts;
>>> };
>>>
>>> and include/linux/spi/flash.h has this:
>>>
>>> struct flash_platform_data {
>>> ? ? ?char ? ? ? ? ? ?*name;
>>> ? ? ?struct mtd_partition *parts;
>>> ? ? ?unsigned int ? ?nr_parts;
>>>
>>> ? ? ?char ? ? ? ? ? ?*type;
>>>
>>> ? ? ?/* we'll likely add more ... use JEDEC IDs, etc */
>>> };
>>>
>>> Should anything be done?
>>
>> How about unifying them both?
>
> That would make sense. ?But the include location would be strange.
>
> The <asm/mach/flash.h> file is used by various arch/arm/mach-* files and in a
> couple of drivers/mtd/maps/*.c files.
>
> The <linux/spi/flash.h> file is also used by various arch/arm/mach-* files as
> well as some arch/blackfin and arch/mips files. ?It's also used by some
> drivers in drivers/mtd/devices and by drivers/spi/spi_butterfly.c.
>
> Because of the multi architecture use, the unifying should be done in the
> include/linux/spi/flash.h file. ?But this include in the various platform
> init's might seem "strange" since the flash is not "spi".
>
> I guess the other option would be to rename the spi version to something like:
>
> struct spi_flash_data {
> ? ? ? ?...
> };
>
> Any comments from the mtd people?
Or just move the definition to an mtd include file. Renaming the
structure probably isn't worth the effort.
g.
prev parent reply other threads:[~2010-04-29 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 20:06 Potential namespace problem for 'struct flash_platfrom_data' H Hartley Sweeten
2010-04-29 20:19 ` Russell King - ARM Linux
2010-04-29 20:35 ` H Hartley Sweeten
2010-04-29 22:47 ` Grant Likely [this message]
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=n2nfa686aa41004291547wb6a1c67bq4d4c7140cb3fcddc@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
/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).