public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Rogan Dawes <lists@dawes.za.net>
Cc: Adrian Bunk <bunk@kernel.org>,
	chris@zankel.net, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] xtensa: don't offer PARPORT_PC
Date: Mon, 14 Apr 2008 22:34:09 +0100	[thread overview]
Message-ID: <20080414223409.5ae3271c@core> (raw)
In-Reply-To: <4803BF9D.4070304@dawes.za.net>

> Pardon a possibly stupid question here, but would it not make more sense 
> to code the architectures for which these various devices *are* 
> possible, rather than requiring each architecture to go through the 
> entire config file and add their own "we don't do this" for many entries?

For any with PCI bus the right fix is to add the header files.
-- 
--
	"Alan, I'm getting a bit worried about you."
				-- Linus Torvalds

  reply	other threads:[~2008-04-14 21:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 19:55 [2.6 patch] xtensa: don't offer PARPORT_PC Adrian Bunk
2008-04-14 20:33 ` Rogan Dawes
2008-04-14 21:34   ` Alan Cox [this message]
2008-04-14 21:31 ` Alan Cox
2008-04-14 22:13   ` Adrian Bunk
2008-04-14 23:00     ` Chris Zankel

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=20080414223409.5ae3271c@core \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=bunk@kernel.org \
    --cc=chris@zankel.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@dawes.za.net \
    /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