public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Pool <mbp@sourcefrog.net>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] turn off CONFIG_FD on ia64?
Date: Tue, 26 Aug 2003 00:28:47 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106185788101534@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106015002132453@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

On 25 Aug 2003 05:30:30 -0400
Jes Sorensen <jes@wildopensource.com> wrote:

> >>>>> "Christoph" == Christoph Hellwig <hch@infradead.org> writes:
> 
> Christoph> Anyway, we should test explicitly for configurations
> Christoph> supported by floppy.c.  So far this would be:
> 
> Christoph> CONFIG_ISA CONFIG_M68K CONFIG_SPARC
> 
> CONFIG_SPARC64 I believe. No idea about MIPS configurations.

Should I send a patch to turn off architectures which will never work? 
(Who to?)  It seems to me that allowing people to turn on options which
don't build is not very helpful.

-- 
Martin 

GNU does not eliminate all the world's problems, only some of them.
		-- The GNU Manifesto

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-08-26  0:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06  6:06 [patch] turn off CONFIG_FD on ia64? David Mosberger
2003-08-06  6:19 ` Martin Pool
2003-08-06  6:33 ` David Mosberger
2003-08-06 19:35 ` Matt Domsch
2003-08-25  9:03 ` Jes Sorensen
2003-08-25  9:21 ` Christoph Hellwig
2003-08-25  9:30 ` Jes Sorensen
2003-08-25 17:05 ` Grant Grundler
2003-08-25 17:27 ` Randy.Dunlap
2003-08-25 18:21 ` Matthew Wilcox
2003-08-25 23:13 ` Grant Grundler
2003-08-26  0:28 ` Martin Pool [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-06  6:00 Martin Pool

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=marc-linux-ia64-106185788101534@msgid-missing \
    --to=mbp@sourcefrog.net \
    --cc=linux-ia64@vger.kernel.org \
    /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