From: Greg KH <greg@kroah.com>
To: Martyn Welch <martyn.welch@gefanuc.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
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 09:44:28 -0700 [thread overview]
Message-ID: <20090911164428.GA17883@kroah.com> (raw)
In-Reply-To: <4AAA7AEB.803@gefanuc.com>
On Fri, Sep 11, 2009 at 05:29:31PM +0100, Martyn Welch wrote:
> Greg KH 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?
> >
> > Martyn, maybe we should rename CONFIG_VME to CONFIG_VME_BUS ?
> >
> > thanks,
> >
> > greg k-h
> >
> Agreed - Not good.
>
> I'll try and rustle up a patch ASAP, but it might not be until Monday
> now - I unfortunately have a rather busy weekend. I'm more than happy
> with CONFIG_VME_BUS if someone beats me to it.
I'll go do it right now.
thanks,
greg k-h
next prev parent reply other threads:[~2009-09-11 16:46 UTC|newest]
Thread overview: 7+ 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 14:26 ` Geert Uytterhoeven
2009-09-11 15:02 ` Greg KH
2009-09-11 16:29 ` Martyn Welch
2009-09-11 16:44 ` Greg KH [this message]
2009-09-11 17:22 ` Geert Uytterhoeven
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=20090911164428.GA17883@kroah.com \
--to=greg@kroah.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=martyn.welch@gefanuc.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.