From: alexis.rodet@bvs-tech.com (Alexis RODET)
To: linux-arm-kernel@lists.infradead.org
Subject: Devel error: redefinition of 'struct flash_platform_data'
Date: Wed, 17 Nov 2010 16:40:06 +0100 [thread overview]
Message-ID: <4CE3F756.6040700@bvs-tech.com> (raw)
Hello,
I'm making an arm machine with both mtd flash and m25p spi flash and try
to define partitions for both chips in my code.
But there are 2 definitions of 'struct flash_platform_data' and both
definition are incompatible:
in <asm/mach/flash.h>:
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;
};
in <linux/spi/flash.h>:
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 */
};
Both are included in a lot of machines or driver.
I don't know what to do.
Which one should I jeopardize or rename ?
Thank for your help,
Alexis RODET
-------------- next part --------------
A non-text attachment was scrubbed...
Name: alexis_rodet.vcf
Type: text/x-vcard
Size: 315 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20101117/80bb9b43/attachment-0001.vcf>
next reply other threads:[~2010-11-17 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 15:40 Alexis RODET [this message]
2010-11-17 16:05 ` Devel error: redefinition of 'struct flash_platform_data' Russell King - ARM Linux
2010-11-19 17:23 ` [PATCH] Renaming 'struct flash_platform_data' into 'struct spi_flash_platform_data' in include/linux/spi/flash.h Alexis RODET
2010-11-21 4:47 ` Baruch Siach
2010-11-22 9:58 ` Alexis RODET
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=4CE3F756.6040700@bvs-tech.com \
--to=alexis.rodet@bvs-tech.com \
--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).