From: Jeff Garzik <jeff@garzik.org>
To: Peer Chen <peerchen@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
akpm <akpm@linux-foundation.org>, htejun <htejun@gmail.com>
Subject: Re: [PATCH] ahci: Add MCP73/MCP77 support to AHCI driver
Date: Sat, 09 Jun 2007 22:43:34 -0400 [thread overview]
Message-ID: <466B6556.8010500@garzik.org> (raw)
In-Reply-To: <200706071805105304242@gmail.com>
Peer Chen wrote:
> Add the MCP73/MCP77 support to ahci driver.
> The patch base on kernel 2.6.22-rc4
>
> Signed-off-by: Peer Chen <peerchen@gmail.com>
applied
Please put comments that should not be copied into the permanent kernel
changelog following a "---" separator, as described in
Documentation/SubmittingPatches. The sentence "The patch base on kernel
2.6.22-rc4" had to be hand-edited out, before automatic patch merge
scripts merged your patch.
next prev parent reply other threads:[~2007-06-10 2:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 10:05 [PATCH] ahci: Add MCP73/MCP77 support to AHCI driver Peer Chen
2007-06-07 10:18 ` Tejun Heo
2007-06-10 2:43 ` Jeff Garzik [this message]
[not found] <15F501D1A78BD343BE8F4D8DB854566B14BFA227@hkemmail01.nvidia.com>
2007-06-07 6:52 ` Tejun Heo
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=466B6556.8010500@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peerchen@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.