From: Tejun Heo <htejun@gmail.com>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org,
brazilnut@linux.vnet.ibm.com
Subject: Re: [PATCH 1/1] libata: Initialize nbytes for internal sg commands
Date: Thu, 01 Feb 2007 10:26:36 +0900 [thread overview]
Message-ID: <45C141CC.6010008@gmail.com> (raw)
In-Reply-To: <1170178343430-patch-mail.ibm.com>
Brian King wrote:
> Some LLDDs, like ipr, use nbytes and pad_len to determine
> the total data transfer length of a command. Make sure
> nbytes gets initialized for internally generated commands.
>
> Signed-off-by: Brian King <brking@linux.vnet.ibm.com>
Acked-by: Tejun Heo <htejun@gmail.com>
--
tejun
next parent reply other threads:[~2007-02-01 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1170178343430-patch-mail.ibm.com>
2007-02-01 1:26 ` Tejun Heo [this message]
2007-02-02 16:54 ` [PATCH 1/1] libata: Initialize nbytes for internal sg commands Jeff Garzik
2007-01-30 17:32 Brian King
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=45C141CC.6010008@gmail.com \
--to=htejun@gmail.com \
--cc=brazilnut@linux.vnet.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=jgarzik@pobox.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).