From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org
Cc: linux-ide@vger.kernel.org, alan@lxorguk.ukuu.org.uk, alan@redhat.com
Subject: Re: [patch 25/30] pata_hpt3x3: clean up by using cable method
Date: Tue, 06 Mar 2007 06:59:54 -0500 [thread overview]
Message-ID: <45ED57BA.4000800@garzik.org> (raw)
In-Reply-To: <200703061038.l26AcAVD019539@shell0.pdx.osdl.net>
akpm@linux-foundation.org wrote:
> From: Alan Cox <alan@lxorguk.ukuu.org.uk>
>
> Signed-off-by: Alan Cox <alan@redhat.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/ata/pata_hpt3x3.c | 22 ++--------------------
> 1 file changed, 2 insertions(+), 20 deletions(-)
dropped patches 9-25.
they should all be rolled up into a single "update ->cable_detect hook"
patch, as discussed.
next prev parent reply other threads:[~2007-03-06 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 10:38 [patch 25/30] pata_hpt3x3: clean up by using cable method akpm
2007-03-06 11:59 ` Jeff Garzik [this message]
2007-03-06 15:19 ` Alan Cox
2007-03-06 14:25 ` Jeff Garzik
2007-03-06 16:27 ` Alan Cox
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=45ED57BA.4000800@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.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).