From: Tejun Heo <htejun@gmail.com>
To: akpm@linux-foundation.org
Cc: jeff@garzik.org, linux-ide@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [patch 05/20] pata_acpi-restore-driver versus libata-clean-up-sff-init-mess
Date: Fri, 11 May 2007 13:43:27 +0200 [thread overview]
Message-ID: <464456DF.5010506@gmail.com> (raw)
In-Reply-To: <200705110548.l4B5mlAh007627@shell0.pdx.osdl.net>
akpm@linux-foundation.org wrote:
> From: Andrew Morton <akpm@linux-foundation.org>
>
> If you apply both libata-clean-up-sff-init-mess.patch and
> pata_acpi-restore-driver.patch, you'll need to add this patch to
> pata_acpi-restore-driver.patch
>
> Cc: Tejun Heo <htejun@gmail.com>
> Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Patch looks good to me. It depends on how Jeff decides on
libata-clean-up-sff-init-mess tho.
--
tejun
prev parent reply other threads:[~2007-05-11 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 5:48 [patch 05/20] pata_acpi-restore-driver versus libata-clean-up-sff-init-mess akpm
2007-05-11 11:43 ` Tejun Heo [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=464456DF.5010506@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--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).