From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Li Yang <leoli@freescale.com>
Subject: Re: libata: kill now unused n_iter and fix sata_fsl
Date: Wed, 06 Feb 2008 07:03:45 -0500 [thread overview]
Message-ID: <47A9A221.9050403@garzik.org> (raw)
In-Reply-To: <47A7EED3.2050801@gmail.com>
Tejun Heo wrote:
> From: James Bottomley <James.Bottomley@HansenPartnership.com>
>
> qc->n_iter was used for libata's own sg walking before sg chaining
> replaced it. During conversion, the field and its usage in sata_fsl
> were left behind. Kill the filed and update sata_fsl.
>
> tj: This was part of James's libata-use-block-layer-padding patch.
> Separated out by me.
>
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> Cc: Li Yang <leoli@freescale.com>
applied
prev parent reply other threads:[~2008-02-06 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 5:06 libata: kill now unused n_iter and fix sata_fsl Tejun Heo
2008-02-06 12:03 ` 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=47A9A221.9050403@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=htejun@gmail.com \
--cc=leoli@freescale.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).