From: "Randy.Dunlap" <rddunlap@osdl.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] disable legacy floppy related ioctl32s
Date: Tue, 30 Sep 2003 22:14:28 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106496057330928@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106495318021597@msgid-missing>
On Tue, 30 Sep 2003 16:10:23 -0600 Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
| On Tuesday 30 September 2003 3:01 pm, Randy.Dunlap wrote:
| > On Tue, 30 Sep 2003 14:55:00 -0600 Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
| > | BTW, it looks like one can still select legacy floppy support on ia64:
| > |
| > | config BLK_DEV_FD
| > | tristate "Normal floppy disk support"
| > | depends on !X86_PC9800 && !ARCH_S390
| >
| > Yes, I submitted a patch for that (and others), but it was rejected
| > by reasoning that we can't and don't want to keep up with fixing
| > all of these...
|
| Heh. Your patch (http://www.ussg.iu.edu/hypermail/linux/kernel/0308.3/0320.html)
| contained:
|
| config BLK_DEV_FD
| tristate "Normal floppy disk support"
| - depends on !X86_PC9800
| + depends on !X86_PC9800 && !IA64
|
| so obviously somebody decided it was reasonable to do it for s390, but
| not for ia64 :-) I didn't see the rejection rationale on the list, but
| it's hard enough to build a working .config without distractions like
| being asked about drivers that can't possibly work (and probably don't
| even compile) on my architecture.
Yes, it was a private rejection.
Yes, one does not always get the same answer when asked multiple times.
I'm all for it, but some people weren't.
--
~Randy
next prev parent reply other threads:[~2003-09-30 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 20:16 [PATCH] disable legacy floppy related ioctl32s Arun Sharma
2003-09-30 20:55 ` Bjorn Helgaas
2003-09-30 21:01 ` Randy.Dunlap
2003-09-30 22:10 ` Bjorn Helgaas
2003-09-30 22:14 ` Randy.Dunlap [this message]
2003-09-30 22:18 ` Arun Sharma
2003-10-01 0:01 ` Arun Sharma
2003-10-01 1:19 ` Matthew Wilcox
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-106496057330928@msgid-missing \
--to=rddunlap@osdl.org \
--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