From: Geert Uytterhoeven <geert@linux-m68k•org>
To: Greg KH <greg@kroah•com>
Cc: Martyn Welch <martyn.welch@gefanuc•com>,
linux-kernel@vger•kernel.org,
Linux-Next <linux-next@vger•kernel.org>
Subject: Re: drivers/staging/vme/Kconfig:5:warning: type of 'VME' redefined from 'boolean' to 'tristate'
Date: Fri, 11 Sep 2009 19:22:16 +0200 [thread overview]
Message-ID: <10f740e80909111022t50d8beb9qf94cfd13413fb29e@mail.gmail.com> (raw)
In-Reply-To: <20090911150210.GB16593@kroah.com>
On Fri, Sep 11, 2009 at 17:02, Greg KH<greg@kroah•com> wrote:
> On Fri, Sep 11, 2009 at 04:26:36PM +0200, Geert Uytterhoeven wrote:
>> 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
>
> Ah, not good.
>
> Are these a board-specific thing? It's not the "VME bus" is it?
These are to enable support for the original VME-based machines (VME
started it's life on m68k).
From a historical point of view, it's a bit funny to see the new
CONFIG_VME(_BUS) depends on PCI ;-)
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
prev parent reply other threads:[~2009-09-11 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 14:26 drivers/staging/vme/Kconfig:5:warning: type of 'VME' redefined from 'boolean' to 'tristate' Geert Uytterhoeven
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 [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=10f740e80909111022t50d8beb9qf94cfd13413fb29e@mail.gmail.com \
--to=geert@linux-m68k$(echo .)org \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=martyn.welch@gefanuc$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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