From: Jeff Garzik <jgarzik@pobox.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Arnd Bergmann <arnd@arndb.de>,
"Robert M. Stockmann" <stock@stokkie.net>,
linux-kernel@vger.kernel.org
Subject: Re: SATA disk device naming ?
Date: Thu, 15 Jul 2004 14:07:15 -0400 [thread overview]
Message-ID: <40F6C7D3.1070005@pobox.com> (raw)
In-Reply-To: <200407151937.43862.bzolnier@elka.pw.edu.pl>
Bartlomiej Zolnierkiewicz wrote:
> On Wednesday 14 of July 2004 13:20, Arnd Bergmann wrote:
>
>>On Dienstag, 13. Juli 2004 05:04, Jeff Garzik wrote:
>>
>>>Whoever builds your kernels changed around the kernel configuration on
>>>you.
>>>
>>>SATA "disk naming" (what driver you use) did not change from 2.6.3 to
>>>2.6.7.
>>
>>The thing that changed is the new BLK_DEV_IDE_SATA option that defaults
>>to 'n', while before it was enabled implicitly.
>
>
> This is a quite fresh change (post 2.6.7) and should be fixed before 2.6.8.
> This option should default to 'y', we can put some runtime warning instead.
>
> Jeff, do you agree?
It's a really tough question... default=n will eliminate a lot of
problems people are reporting on lkml, but default=y changes the disks
for the few users not having problems.
It's a tough call...
Jeff
next prev parent reply other threads:[~2004-07-15 18:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 2:25 SATA disk device naming ? Robert M. Stockmann
2004-07-13 3:04 ` Jeff Garzik
2004-07-14 11:20 ` Arnd Bergmann
2004-07-15 17:37 ` Bartlomiej Zolnierkiewicz
2004-07-15 18:07 ` Jeff Garzik [this message]
2004-07-13 6:46 ` Eric D. Mudama
2004-07-13 13:24 ` Ian Soboroff
2004-07-13 16:23 ` Ricky Beam
2004-07-13 16:49 ` Jeff Garzik
2004-07-13 17:29 ` Tigran Aivazian
2004-07-13 22:35 ` Chris Wedgwood
2004-07-14 9:48 ` P
2004-07-15 2:44 ` Joel Becker
2004-07-25 19:05 ` Greg KH
2004-07-13 17:15 ` Tigran Aivazian
2004-07-13 16:58 ` Muli Ben-Yehuda
-- strict thread matches above, loose matches on Subject: below --
2004-07-14 0:09 DaMouse
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=40F6C7D3.1070005@pobox.com \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stock@stokkie.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