From: Jeff Garzik <jeff@garzik.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Lin Ming <ming.m.lin@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git patches] libata updates for 3.3
Date: Tue, 17 Jan 2012 11:51:53 -0500 [thread overview]
Message-ID: <4F15A729.4000600@garzik.org> (raw)
In-Reply-To: <CA+55aFzNpK0z2A8-0v2bLEX_Wma5f3tkeSVjAdwpkrW0=3V_Wg@mail.gmail.com>
On 01/17/2012 12:19 AM, Linus Torvalds wrote:
> On Mon, Jan 16, 2012 at 9:16 PM, Lin Ming<ming.m.lin@intel.com> wrote:
>>
>> But ata port async suspend was not enabled in above patch.
>> So I think this is a regression.
>
> Ok. Jeff? Should I take that patch directly, or will you take it?
Coming today, with at least one other change... still keeping an eye
out for possible PM problems on older non-AHCI SATA hardware.
Jeff
next prev parent reply other threads:[~2012-01-17 16:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 0:32 [git patches] libata updates for 3.3 Jeff Garzik
2012-01-14 5:21 ` Linus Torvalds
2012-01-15 14:41 ` Jeff Garzik
2012-01-16 1:15 ` Lin Ming
2012-01-16 5:23 ` Lin Ming
2012-01-16 19:25 ` Linus Torvalds
2012-01-16 19:29 ` Linus Torvalds
2012-01-16 19:55 ` Linus Torvalds
2012-01-17 5:16 ` Lin Ming
2012-01-17 5:19 ` Linus Torvalds
2012-01-17 16:51 ` Jeff Garzik [this message]
2012-01-17 17:00 ` Jeff Garzik
2012-01-16 19:42 ` Alan Cox
2012-01-16 19:47 ` Linus Torvalds
2012-01-16 19:54 ` Alan Cox
2012-01-16 20:02 ` Linus Torvalds
2012-01-16 20:21 ` Linus Torvalds
2012-01-16 20:27 ` Jeff Garzik
2012-01-16 23:54 ` Alan Cox
2012-01-17 0:02 ` Linus Torvalds
2012-01-17 0:18 ` Matthew Garrett
2012-01-16 21:26 ` Matthew Garrett
2012-01-16 21:34 ` Linus Torvalds
2012-01-16 22:03 ` Matthew Garrett
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=4F15A729.4000600@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=torvalds@linux-foundation.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 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.