From: Jeff Garzik <jeff@garzik.org>
To: IDE/ATA development list <linux-ide@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>, Kuan Luo <kluo@nvidia.com>,
Mark Lord <liml@rtr.ca>, Alan <alan@lxorguk.ukuu.org.uk>
Subject: libata-dev.git rebased; ACPI turned on
Date: Fri, 05 Oct 2007 16:46:06 -0400 [thread overview]
Message-ID: <4706A28E.7080306@garzik.org> (raw)
1) I just rebased libata-dev.git and all its branches. If you are
unfamiliar with git rebasing, this means you must either re-clone, or
force-update your branch like this:
# grab latest nv-swncq branch
URL=git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
cd /local/repo/libata-dev
git-checkout master # or any branch other than what
# is being updated
git-fetch -f $URL nv-swncq:nv-swncq # force update of 'nv-swncq'
2) libata ACPI support has been turned on by default. So let's be alert
for problems related to that. Problems will _probably_ fall into one of
those categories:
* suspend/resume glitches
* problems related to the new ATA commands we are sending to the drive,
as passed to us from the BIOS ACPI tables
On the upside, this should make libata suspend/resume a lot more sane.
3) I had to yank the FIFO drain patch. Alan says that the FIFO drain
patch that went in causes problems on some chips, and that we cannot
apply it unconditionally to all SFF controllers. He recommends a new
->drain_fifo() hook, with a default ata_sff_drain_fifo() implementation
matching what Mark Lord previously submitted.
Jeff
P.S. I still have some more patches to apply, but they should not
require a rebase.
reply other threads:[~2007-10-05 20: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=4706A28E.7080306@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kluo@nvidia.com \
--cc=len.brown@intel.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).