From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: wuzhangjin@gmail.com
Cc: Jeff Chua <jeff.chua.linux@gmail.com>,
Etienne Basset <etienne.basset@numericable.fr>,
David Miller <davem@davemloft.net>,
rjw@sisk.pl, linux-kernel@vger.kernel.org,
kernel-testers@vger.kernel.org,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, linux-ide@vger.kernel.org
Subject: Re: [Bug #13663] suspend to ram regression (IDE related)
Date: Mon, 6 Jul 2009 16:57:59 +0200 [thread overview]
Message-ID: <200907061658.00936.bzolnier@gmail.com> (raw)
In-Reply-To: <1246635096.16890.6.camel@falcon>
On Friday 03 July 2009 17:31:36 Wu Zhangjin wrote:
> Hi,
>
> > OK, I see another gotcha added by recent changes, we need to explicitly
> > initialize rq_in_flight variables now. Revised patch below..
> >
>
> Sorry, STD also not work. if apply this patch, the same problem as not
> apply it, it stopped at:
>
> ...
> PM: Crete hibernation image:
> PM: Need to copy ... pages
> PM: Hibernation image created ...
>
> I think it's better to revert this commit:
> a1317f714af7aed60ddc182d0122477cbe36ee9b ("ide: improve handling of
> Power Management requests")
I completely agree and I've already requested this a week ago
(this commit was not meant for going straight to -rc tree anyway).
next prev parent reply other threads:[~2009-07-06 14:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <etTXaRqGgAC.A.SaE.6iASKB@chimera>
[not found] ` <5Hhc7UkUKEO.A.RvE.BjASKB@chimera>
[not found] ` <4A489775.6020102@numericable.fr>
[not found] ` <20090629.033730.193709457.davem@davemloft.net>
[not found] ` <4A48E307.2010208@numericable.fr>
[not found] ` <b6a2187b0906290921w15afd443qccb943ccfd48688b@mail.gmail.com>
[not found] ` <b6a2187b0907010731k510150b5u1c7fce8cbed7c33b@mail.gmail.com>
[not found] ` <b6a2187b0907010731k510150b5u1c7fce8cbed7c33b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-01 14:47 ` [Bug #13663] suspend to ram regression (IDE related) Wu Zhangjin
2009-07-01 16:21 ` Bartlomiej Zolnierkiewicz
[not found] ` <200907011821.26091.bzolnier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-07-01 16:29 ` Bartlomiej Zolnierkiewicz
[not found] ` <200907011829.16850.bzolnier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-07-01 17:28 ` Jeff Chua
[not found] ` <b6a2187b0907011028r27d35be4xc62c7ed4496dfb2f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-01 21:30 ` Etienne Basset
2009-07-02 1:46 ` Wu Zhangjin
2009-07-02 2:09 ` Jeff Chua
2009-07-02 10:46 ` Ralf Baechle
2009-07-02 16:13 ` Bartlomiej Zolnierkiewicz
[not found] ` <200907021813.57322.bzolnier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-07-03 3:58 ` Wu Zhangjin
2009-07-03 4:06 ` Wu Zhangjin
2009-07-03 13:08 ` Bartlomiej Zolnierkiewicz
2009-07-03 15:31 ` Wu Zhangjin
2009-07-06 14:57 ` Bartlomiej Zolnierkiewicz [this message]
2009-07-06 19:22 ` David Miller
2009-06-28 22:57 [Bug 13663] New: " bugzilla-daemon
2009-06-28 22:57 ` [Bug 13663] " bugzilla-daemon
2009-06-29 23:25 ` bugzilla-daemon
2009-07-07 20:32 ` bugzilla-daemon
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=200907061658.00936.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--cc=etienne.basset@numericable.fr \
--cc=jeff.chua.linux@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=rjw@sisk.pl \
--cc=wuzhangjin@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).