From: Tejun Heo <htejun@gmail.com>
To: jeff@garzik.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/5] libata: prefer hardreset
Date: Mon, 28 Jan 2008 11:47:13 +0900 [thread overview]
Message-ID: <479D4231.7090605@gmail.com> (raw)
In-Reply-To: <479D416A.7040007@gmail.com>
Tejun Heo wrote:
> Tejun Heo wrote:
>> - /* prereset() might have modified ehc->i.action */
>> - if (ehc->i.action & ATA_EH_HARDRESET)
>> - reset = hardreset;
>> - else if (ehc->i.action & ATA_EH_SOFTRESET)
>> - reset = softreset;
>> - else {
>
> Seems we'll need this chunk. Will post updated version.
Eeeeek... Never mind. I was confused. Sorry about the noise.
--
tejun
next prev parent reply other threads:[~2008-01-28 2:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 15:21 [PATCHSET libata-dev#upstream] libata: prefer hardreset Tejun Heo
2008-01-23 15:21 ` [PATCH 1/5] " Tejun Heo
2008-01-28 2:43 ` Tejun Heo
2008-01-28 2:47 ` Tejun Heo [this message]
2008-01-23 15:21 ` [PATCH 2/5] libata: kill ATA_LFLAG_HRST_TO_RESUME Tejun Heo
2008-01-23 15:21 ` [PATCH 3/5] libata: kill ATA_EHI_RESUME_LINK Tejun Heo
2008-01-23 15:21 ` [PATCH 4/5] libata: kill ATA_LFLAG_SKIP_D2H_BSY Tejun Heo
2008-01-23 15:21 ` [PATCH 5/5] libata: kill ata_ehi_schedule_probe() Tejun Heo
2008-02-01 20:17 ` [PATCHSET libata-dev#upstream] libata: prefer hardreset Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2008-03-11 3:41 [PATCHSET libata-dev#upstream] libata: prefer hardreset, take #2 Tejun Heo
2008-03-11 3:41 ` [PATCH 1/5] libata: prefer hardreset Tejun Heo
2008-03-11 4:27 [PATCHSET #upstream-fixes] block/libata: update and use block layer padding and draining, take 3 Tejun Heo
2008-03-11 4:27 ` [PATCH 1/5] libata: prefer hardreset 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=479D4231.7090605@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--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).