From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, linux-m68k@vger.kernel.org,
linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Chen Liqin <liqin.chen@sunplusct.com>,
Paul Mackerras <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>,
sparclinux@vger.kernel.org, Guan Xuetao <gxt@mprc.pku.edu.cn>,
Lennox Wu <lennox.wu@gmail.com>,
linux-arch@vger.kernel.org,
Jesper Nilsson <jesper.nilsson@axis.com>,
Russell King <linux@arm.linux.org.uk>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Helge Deller <deller@gmx.de>,
x86@kernel.org, "James E.J. Bottomley" <jejb@parisc-linux.org>,
Ingo Molnar <mingo@redhat.com>, Matt Turner <mattst88@gmail.com>,
Fenghua Yu <fenghua.yu@intel.com>,
microblaze-uclinux@itee.uq.edu.au,
Chris Metcalf <cmetcalf@tilera.com>,
Mikael Starvik <starvik@axis.com>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Thomas
Subject: Re: [RFC,PATCH] Cleanup PC parallel port Kconfig
Date: Tue, 14 Jun 2011 22:32:08 +0200 [thread overview]
Message-ID: <BANLkTikuVsFS-UbS+Dap2Zy-f1+qLc1TLw@mail.gmail.com> (raw)
In-Reply-To: <20110614190850.GA13526@linux-mips.org>
On Tue, Jun 14, 2011 at 21:08, Ralf Baechle <ralf@linux-mips.org> wrote:
> The PC parallel port Kconfig as acquired one of those messy terms to
> describe it's architecture dependencies:
>
> depends on (!SPARC64 || PCI) && !SPARC32 && !M32R && !FRV && \
> (!M68K || ISA) && !MN10300 && !AVR32 && !BLACKFIN
>
> This isn't just ugly - it also almost certainly describes the dependencies
> too coarse grainedly. This is an attempt at cleaing the mess up.
> --- a/arch/m68k/Kconfig.mmu
> +++ b/arch/m68k/Kconfig.mmu
> @@ -399,6 +399,7 @@ config ISA
> bool
> depends on Q40 || AMIGA_PCMCIA
> default y
> + select PARPORT_PC
Why do you select PARPORT_PC here instead of HAVE_PC_PARPORT?
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2011-06-14 20:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 19:08 [RFC,PATCH] Cleanup PC parallel port Kconfig Ralf Baechle
2011-06-14 20:22 ` Arnd Bergmann
2011-06-15 8:02 ` Lennox Wu
2011-06-14 20:25 ` H. Peter Anvin
2011-06-14 21:33 ` Arnd Bergmann
2011-06-15 4:30 ` H. Peter Anvin
2011-06-15 7:47 ` Russell King - ARM Linux
2011-06-15 15:08 ` H. Peter Anvin
2011-06-15 15:21 ` Russell King - ARM Linux
2011-06-15 9:46 ` Arnd Bergmann
2011-06-15 11:24 ` Geert Uytterhoeven
2011-06-14 22:34 ` Ralf Baechle
2011-06-15 4:18 ` H. Peter Anvin
2011-06-15 4:40 ` Guenter Roeck
2011-06-15 5:43 ` H. Peter Anvin
2011-06-15 8:34 ` Ralf Baechle
2011-06-15 14:36 ` Guenter Roeck
2011-06-14 20:32 ` Geert Uytterhoeven [this message]
2011-06-14 22:08 ` Luck, Tony
2011-06-15 4:31 ` H. Peter Anvin
2011-06-15 7:39 ` Russell King - ARM Linux
2011-06-15 15:16 ` H. Peter Anvin
2011-06-15 1:24 ` Guan Xuetao
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=BANLkTikuVsFS-UbS+Dap2Zy-f1+qLc1TLw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=benh@kernel.crashing.org \
--cc=cmetcalf@tilera.com \
--cc=deller@gmx.de \
--cc=fenghua.yu@intel.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=hpa@zytor.com \
--cc=ink@jurassic.park.msu.ru \
--cc=jejb@parisc-linux.org \
--cc=jesper.nilsson@axis.com \
--cc=lennox.wu@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=liqin.chen@sunplusct.com \
--cc=mattst88@gmail.com \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=sparclinux@vger.kernel.org \
--cc=starvik@axis.com \
--cc=x86@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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).