From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nick Warne <nick@linicks.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IDE probing IDE_MAX_HWIFS
Date: Sun, 26 Jun 2005 20:33:07 +0100 [thread overview]
Message-ID: <1119814384.28649.44.camel@localhost.localdomain> (raw)
In-Reply-To: <200506261908.12398.nick@linicks.net>
On Sul, 2005-06-26 at 19:08, Nick Warne wrote:
> Heh. Yes I know now, but I was thinking along the lines that if someone knows
> how many IDE interfaces they have it could be specified exactly - I
> didn't/don't see why it is considered an option for config_embedded only to
> be allowed to do that.
Its a trade off. If you allow every configuration option kernel
configuration begins to resemble an inquisition.
next prev parent reply other threads:[~2005-06-26 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-25 11:10 IDE probing IDE_MAX_HWIFS Nick Warne
2005-06-26 17:51 ` Alan Cox
2005-06-26 18:08 ` Nick Warne
2005-06-26 19:33 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-25 13:47 Nick Warne
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=1119814384.28649.44.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.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