From: Tejun Heo <htejun@gmail.com>
To: Fajun Chen <fajunchen@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: How to make SATA hotplug path tight?
Date: Sat, 16 Sep 2006 10:52:09 +0900 [thread overview]
Message-ID: <450B58C9.7010904@gmail.com> (raw)
In-Reply-To: <8202f4270609151248k236d6c24vab519b64902f102e@mail.gmail.com>
Fajun Chen wrote:
> Tejun, I use SATA Sil24. Where should ATA_FLAG_HRST_TO_RESUME be
> flagged? I made one attempt by making the following change in
> libata.h and it seems not working sometimes (see log at the end)? I'm
> a little puzzled by different flags such as ap->flags, ehc->flags...
> Is there any document about new eh?
Add the flag to SIL24_COMMON_FLAGS. No, there is no doc yet. On my
to-do list though.
--
tejun
next prev parent reply other threads:[~2006-09-16 1:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 15:12 How to make SATA hotplug path tight? Fajun Chen
2006-09-15 17:11 ` Leon Woestenberg
2006-09-15 19:40 ` Fajun Chen
2006-09-15 18:09 ` Tejun Heo
2006-09-15 19:48 ` Fajun Chen
2006-09-16 1:52 ` Tejun Heo [this message]
[not found] ` <8202f4270609181218h160b8df7x4853f58429229b3b@mail.gmail.com>
2006-09-19 3:11 ` Tejun Heo
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=450B58C9.7010904@gmail.com \
--to=htejun@gmail.com \
--cc=fajunchen@gmail.com \
--cc=linux-ide@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).