From: Jeff Garzik <jeff@garzik.org>
To: Linux IDE mailing list <linux-ide@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
harry.zhang@amd.com, Shane Huang <Shane.Huang@amd.com>,
turmlos@comcast.net, Tejun Heo <tj@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [RFT] ahci rebase in libata #upstream
Date: Sun, 28 Mar 2010 00:46:35 -0400 [thread overview]
Message-ID: <4BAEDF2B.3020808@garzik.org> (raw)
The 'upstream' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
was just rebased. This is the branch normally exported to linux-next,
and is intended for merging into 2.6.35, when the merge window for
2.6.35 opens.
This rebase merges in ahci changes from torvalds/linux-2.6.git into the
major AHCI driver reorganization authored by Anton Vorontsov, which
creates a new kernel module libahci.
Please test and make sure your ahci driver continues working as expected!
People who have authored patches for ahci, and have not received an
"applied" email acknowledgment need to rebase and resend their changes
on top of the new 'upstream' branch of libata-dev.git.
Jeff
reply other threads:[~2010-03-28 4:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BAEDF2B.3020808@garzik.org \
--to=jeff@garzik.org \
--cc=Shane.Huang@amd.com \
--cc=harry.zhang@amd.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.org \
--cc=turmlos@comcast.net \
/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