From: Michael Ellerman <michael@ellerman.id.au>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, sfr@canb.auug.org.au
Subject: Re: [PATCH] iseries: fix CONFIG_VIOCONS/CONFIG_VT dependency
Date: Wed, 16 May 2007 13:41:59 +1000 [thread overview]
Message-ID: <1179286919.4120.39.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <20070515190343.GA13203@lixom.net>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
On Tue, 2007-05-15 at 14:03 -0500, Olof Johansson wrote:
> VT already depends on !VIOCONS, but there's no restriction in the other
> direction. This makes an allyesconfig not build.
>
> Switch to a Kconfig dependency instead of a compile-time error.
>
>
> Signed-off-by: Olof Johansson <olof@lixom.net>
>
> diff --git a/arch/powerpc/platforms/iseries/Kconfig b/arch/powerpc/platforms/iseries/Kconfig
> index 46c3a8e..e48f018 100644
> --- a/arch/powerpc/platforms/iseries/Kconfig
> +++ b/arch/powerpc/platforms/iseries/Kconfig
> @@ -8,6 +8,7 @@ menu "iSeries device drivers"
>
> config VIOCONS
> tristate "iSeries Virtual Console Support (Obsolete)"
> + depends on !VT
> help
This context doesn't match linus' or the powerpc tree, I see:
config VIOCONS
bool "iSeries Virtual Console Support (Obsolete)"
depends on !HVC_ISERIES
default n
help
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-16 3:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 19:03 [PATCH] iseries: fix CONFIG_VIOCONS/CONFIG_VT dependency Olof Johansson
2007-05-16 3:41 ` Michael Ellerman [this message]
2007-05-16 4:08 ` Olof Johansson
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=1179286919.4120.39.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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).