From: Jeff Garzik <jeff@garzik.org>
To: Greg KH <greg@kroah.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, kevin.huang@rdc.com.tw,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] pata_rdc: driver for RDC ATA devices
Date: Tue, 28 Jul 2009 23:05:19 -0400 [thread overview]
Message-ID: <4A6FBC6F.6040404@garzik.org> (raw)
In-Reply-To: <20090729025307.GA25100@kroah.com>
Greg KH wrote:
> On Tue, Jul 28, 2009 at 09:16:52PM -0400, Jeff Garzik wrote:
>> Alan Cox wrote:
>>> Try this version instead - forgot to refresh the patch before sending
>>>
>>> From: Alan Cox <alan@linux.intel.com>
>>>
>>> Signed-off-by: Alan Cox <alan@linux.intel.com>
>>> ---
>>>
>>> drivers/ata/Kconfig | 10 +
>>> drivers/ata/Makefile | 1
>>> drivers/ata/pata_rdc.c | 400 ++++++++++++++++++++++++++++++++++++++++++++++++
>>> 3 files changed, 411 insertions(+), 0 deletions(-)
>>> create mode 100644 drivers/ata/pata_rdc.c
>> applied... and ata_piix+pata_rdc cleanups queued on todo list
>
> Great! Let me know when this goes to Linus so I delete the one in the
> staging tree.
FWIW, it's in libata-dev.git#upstream and libata-dev.git#NEXT, so
linux-next should pick it up automatically.
Jeff
next prev parent reply other threads:[~2009-07-29 3:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 17:29 [PATCH] pata_rdc: driver for RDC ATA devices Alan Cox
2009-06-24 19:35 ` Jeff Garzik
2009-06-24 22:55 ` Alan Cox
2009-06-24 23:33 ` Joe Perches
2009-06-24 23:38 ` Jeff Garzik
2009-06-25 4:27 ` Kevin Huang (黃凱文)
2009-07-29 1:16 ` Jeff Garzik
2009-07-29 2:53 ` Greg KH
2009-07-29 3:05 ` Jeff Garzik [this message]
2009-07-29 3:37 ` Stephen Rothwell
2009-07-29 13:56 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2009-06-24 17:10 Alan Cox
2009-06-24 16:38 ` Joe Perches
2009-06-24 16:42 ` 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=4A6FBC6F.6040404@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=kevin.huang@rdc.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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