From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Adrian Bunk <bunk@kernel.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Jeff Garzik <jgarzik@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: 2.6.25-rc8-mm2: CONFIG_ATA_SFF: panic involving mount_block_root and down the road
Date: Sun, 13 Apr 2008 09:45:45 +0900 [thread overview]
Message-ID: <480157B9.90801@gmail.com> (raw)
In-Reply-To: <480088AD.1040904@garzik.org>
Jeff Garzik wrote:
>>> Now raise hands those who knew that your ATA controller is SFF
>>> compliant.
/me raises a hand.
>> Is there any technical reason why we have to bother users with the
>> ATA_SFF option at all?
>>
>> It sounds like a perfect canndidate for being select'ed.
>
> 'default y' is appropriate, but option that is used to disable a major
> swath of legacy code unneeded on modern FIS-based SATA platforms like AHCI.
Heh.. yeah, but I have to admit SFF support is cryptic. We can
definitely use some friendly explanation there.
--
tejun
next prev parent reply other threads:[~2008-04-13 0:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080410203354.f0a6f464.akpm@linux-foundation.org>
[not found] ` <20080411234345.GA4742@martell.zuzino.mipt.ru>
2008-04-12 0:59 ` 2.6.25-rc8-mm2: CONFIG_ATA_SFF: panic involving mount_block_root and down the road Alexey Dobriyan
2008-04-12 6:52 ` Adrian Bunk
2008-04-12 10:02 ` Jeff Garzik
2008-04-13 0:45 ` Tejun Heo [this message]
2008-04-13 0:51 ` [mm patch] select ATA_SFF Adrian Bunk
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=480157B9.90801@gmail.com \
--to=htejun@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=jeff@garzik.org \
--cc=jgarzik@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).