From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 01/05] libata: separate out ata_sata_print_link_status
Date: Tue, 17 Jan 2006 19:49:42 -0500 [thread overview]
Message-ID: <43CD90A6.40106@pobox.com> (raw)
In-Reply-To: <20051219133502.GA26769@htj.dyndns.org>
Tejun Heo wrote:
> Separate out ata_sata_print_link_status() from __sata_phy_reset().
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
applied patches 1, 3, 4 to 'upstream-2.6.17' branch
prev parent reply other threads:[~2006-01-18 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 13:35 [PATCH 01/05] libata: separate out ata_sata_print_link_status Tejun Heo
2005-12-19 13:35 ` [PATCH 02/05] libata: export ata_busy_sleep Tejun Heo
2005-12-19 13:36 ` [PATCH 03/05] ahci: separate out ahci_stop/start_engine Tejun Heo
2005-12-19 13:37 ` [PATCH 04/05] ahci: separate out ahci_dev_classify Tejun Heo
2005-12-19 13:38 ` [PATCH 05/05] ahci: rewrite ahci_phy_reset Tejun Heo
2006-01-18 0:49 ` 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=43CD90A6.40106@pobox.com \
--to=jgarzik@pobox.com \
--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).