From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, Linux-Next <linux-next@vger.kernel.org>
Subject: drivers/staging/vme/Kconfig:5:warning: type of 'VME' redefined from 'boolean' to 'tristate'
Date: Fri, 11 Sep 2009 16:26:36 +0200 [thread overview]
Message-ID: <10f740e80909110726x313e3e3coe2321c683163e3a5@mail.gmail.com> (raw)
http://kisskb.ellerman.id.au/kisskb/buildresult/1221192/:
drivers/staging/vme/Kconfig:5:warning: type of 'VME' redefined from
'boolean' to 'tristate'
drivers/staging/vme/Kconfig:5:warning: type of 'VME' redefined from
'boolean' to 'tristate'
We already have:
arch/m68k/Kconfig:config VME
arch/m68k/Kconfig: bool "VME (Motorola and BVM) support"
arch/m68k/Kconfig: Say Y here if you want to build a kernel for
a 680x0 based VME
arch/m68k/Kconfig: depends on VME
arch/m68k/Kconfig: Say Y to include support for early Motorola
VME boards. This will
arch/m68k/Kconfig: depends on VME
arch/m68k/Kconfig: Say Y to include support for Motorola VME
boards. This will build a
arch/m68k/Kconfig: depends on VME
arch/m68k/Kconfig: Say Y to include support for VME boards from
BVM Ltd. This will
arch/m68k/Kconfig: depends on (AMIGA || ATARI || MAC || SUN3 ||
SUN3X || VME || APOLLO) && (ATARI_MFPSER=y || ATARI_SCC=y || AT
fs/partitions/Kconfig: default y if VME
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2009-09-11 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 14:26 Geert Uytterhoeven [this message]
2009-09-11 15:02 ` Greg KH
2009-09-11 16:29 ` Martyn Welch
2009-09-11 16:44 ` Greg KH
2009-09-11 17:22 ` Geert Uytterhoeven
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=10f740e80909110726x313e3e3coe2321c683163e3a5@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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
all inboxes | Powered by JetHome®