linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: David Brownell <david-b@pacbell.net>,
	Russell King <rmk+kernel@arm.linux.org.uk>,
	David Woodhouse <dwmw2@infradead.org>
Cc: Linux Mailing List <linux-kernel@vger.kernel.org>,
	linux-embedded <linux-embedded@vger.kernel.org>
Subject: flash_platform_data namespace collision
Date: Fri, 15 Jan 2010 23:41:15 -0600	[thread overview]
Message-ID: <1263620475.29868.6280.camel@calx> (raw)

I've got a board here with SPI, NOR, and NAND flash devices and I've
just run into a namespace collision on flash_platform_data from

 include/spi/flash.h

and

 arch/arm/include/asm/mach/flash.h

And each appears to have a bunch of users.

-- 
http://selenic.com : development and support for Mercurial and Linux


             reply	other threads:[~2010-01-16  5:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16  5:41 Matt Mackall [this message]
2010-01-16  6:03 ` flash_platform_data namespace collision David Brownell
2010-01-16 11:04 ` Russell King
2010-01-16 17:47   ` Matt Mackall
2010-01-16 19:23     ` David Brownell

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=1263620475.29868.6280.camel@calx \
    --to=mpm@selenic.com \
    --cc=david-b@pacbell.net \
    --cc=dwmw2@infradead.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    /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).