From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH #upstream 1/2] libata-eh: update atapi_eh_request_sense() to take @dev instead of @qc
Date: Fri, 27 Jun 2008 02:41:14 -0400 [thread overview]
Message-ID: <48648B8A.9000500@garzik.org> (raw)
In-Reply-To: <484E4925.30202@gmail.com>
Tejun Heo wrote:
> Update atapi_eh_request_sense() to take @dev, @sense_buf and
> @dfl_sense_key instead of taking @qc and extracting information from
> it. This change is to make the function more generic and allow it to
> be called from other places.
>
> While at it, make cdb initialization use initializer.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> ---
> drivers/ata/libata-eh.c | 19 +++++++++----------
> 1 file changed, 9 insertions(+), 10 deletions(-)
applied
prev parent reply other threads:[~2008-06-27 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 9:28 [PATCH #upstream 1/2] libata-eh: update atapi_eh_request_sense() to take @dev instead of @qc Tejun Heo
2008-06-10 9:28 ` [PATCH #upstream 2/2] libata-eh: clear UNIT ATTENTION after reset Tejun Heo
2008-06-27 6:41 ` Jeff Garzik
2008-08-30 12:20 ` [PATCH #upstream UPDATED " Tejun Heo
2008-09-29 4:34 ` Jeff Garzik
2008-06-27 6:41 ` Jeff Garzik [this message]
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=48648B8A.9000500@garzik.org \
--to=jeff@garzik.org \
--cc=htejun@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).