From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: stable@vger.kernel.org, Michael Schmitt <tcwardrobe@gmail.com>,
Jeff Garzik <jgarzik@pobox.com>,
Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>,
cwillu <cwillu@cwillu.com>, Mark Lord <kernel@teksavvy.com>,
Tejun Heo <htejun@gmail.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH 3.3.y] libata: forbid port runtime pm by default, fixing regression
Date: Fri, 25 May 2012 02:30:17 +0900 [thread overview]
Message-ID: <20120524173017.GA28703@kroah.com> (raw)
In-Reply-To: <20120519235854.GA32208@burratino>
On Sat, May 19, 2012 at 06:58:54PM -0500, Jonathan Nieder wrote:
> From: Lin Ming <ming.m.lin@intel.com>
> Date: Wed, 18 Apr 2012 09:29:47 +0800
>
> commit 0c8d32c27f5cf6e14ca14b4758d1e994eebd50fd upstream.
>
> Forbid port runtime pm by default because it has known hotplug issue.
> User can allow it by, for example
>
> echo auto > /sys/devices/pci0000:00/0000:00:1f.2/ata2/power/control
>
> Signed-off-by: Lin Ming <ming.m.lin@intel.com>
> Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
> ---
> Hi Greg,
>
> Please consider
>
> 0c8d32c27f5c libata: forbid port runtime pm by default, fixing
> regression
>
> for inclusion in the 3.3-stable tree. (It should apply there cleanly.
> The copy in this message is just for easy reference.)
Now applied, thanks for letting me know.
greg k-h
next prev parent reply other threads:[~2012-05-24 21:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 20:38 Hotplug borked after suspend/resume in Linux-3.3 ? Mark Lord
2012-04-17 20:48 ` Mark Lord
2012-04-17 20:51 ` Tejun Heo
2012-04-17 20:53 ` Mark Lord
2012-04-17 21:02 ` Mark Lord
2012-04-17 21:05 ` cwillu
2012-04-18 17:10 ` Martin Mokrejs
2012-04-18 17:29 ` Jeff Garzik
2012-04-18 17:44 ` Martin Mokrejs
2012-04-18 18:23 ` Martin Mokrejs
2012-04-18 18:32 ` Martin Mokrejs
2012-04-19 1:31 ` Lin Ming
[not found] ` <CAF1ivSYqzjv10F+sdYkR_jdTZvzKP1=_ZwgNDj2njnmb6uaenA@mail.gmail.com>
2012-04-19 8:16 ` Lin Ming
2012-04-19 17:28 ` Martin Mokrejs
2012-04-19 18:22 ` Martin Mokrejs
2012-04-20 1:46 ` Lin Ming
2012-04-20 2:37 ` Grant Grundler
2012-04-26 9:29 ` Gwendal Grignou
2012-04-26 13:06 ` Lin Ming
2012-04-26 16:50 ` Gwendal Grignou
2012-05-03 1:26 ` Lin Ming
2012-05-19 23:58 ` [PATCH 3.3.y] libata: forbid port runtime pm by default, fixing regression Jonathan Nieder
2012-05-24 17:30 ` Greg KH [this message]
2012-04-17 21:04 ` Hotplug borked after suspend/resume in Linux-3.3 ? Jeff Garzik
2012-04-17 20:57 ` Jeff Garzik
2012-04-17 21:05 ` Mark Lord
2012-04-17 21:10 ` Jeff Garzik
2012-04-17 21:16 ` Mark Lord
[not found] ` <CAF1ivSbEWJ18vV1ZqTnzWuZ5AXKwj+0pPPzCWUmnT_JKwKKQ2w@mail.gmail.com>
2012-04-18 1:29 ` Lin Ming
2012-04-18 1:37 ` Mark Lord
2012-04-18 1:46 ` Mark Lord
2012-04-18 6:18 ` Jeff Garzik
2012-04-18 1:52 ` Lin Ming
2012-04-18 2:28 ` Jeff Garzik
2012-04-17 20:50 ` Jeff Garzik
2012-04-17 21:07 ` Mark Lord
2012-04-17 21:14 ` Mark Lord
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=20120524173017.GA28703@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cwillu@cwillu.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=jrnieder@gmail.com \
--cc=kernel@teksavvy.com \
--cc=linux-ide@vger.kernel.org \
--cc=mmokrejs@fold.natur.cuni.cz \
--cc=stable@vger.kernel.org \
--cc=tcwardrobe@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 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).