public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>
Subject: Re: [Bugme-new] [Bug 14365] New: resume from suspend to ram broken after suspend to disk
Date: Sat, 10 Oct 2009 23:30:33 +0200	[thread overview]
Message-ID: <200910102330.33297.rjw@sisk.pl> (raw)
In-Reply-To: <20091010103905.7bc562c3.akpm@linux-foundation.org>

On Saturday 10 October 2009, Andrew Morton wrote:
> On Sat, 10 Oct 2009 13:40:45 GMT bugzilla-daemon@bugzilla.kernel.org wrote:
> 
> > http://bugzilla.kernel.org/show_bug.cgi?id=14365
> > 
> >            Summary: resume from suspend to ram broken after suspend to
> >                     disk
> >            Product: Power Management
> >            Version: 2.5
> >     Kernel Version: 2.6.31
> >           Platform: All
> >         OS/Version: Linux
> >               Tree: Mainline
> >             Status: NEW
> >           Severity: normal
> >           Priority: P1
> >          Component: Hibernation/Suspend
> >         AssignedTo: power-management_other@kernel-bugs.osdl.org
> >         ReportedBy: corsac@debian.org
> >         Regression: No
> 
> It worries me that we have both "Power management, Hibernation/Suspend"
> and acpi-power-sleep-wake.
> 
> Are these duplicative?

acpi-power-sleep-wake is more specific.  Hibernation/Suspend bugs need not be.
about ACPI.

> Should we kill one off?

I don't think that's necessary.

> Do the acpi developers monitor the "Power Management" category?

Yes, they do, to my knowledge.

      reply	other threads:[~2009-10-10 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-14365-10286@http.bugzilla.kernel.org/>
2009-10-10 17:39 ` [Bugme-new] [Bug 14365] New: resume from suspend to ram broken after suspend to disk Andrew Morton
2009-10-10 21:30   ` Rafael J. Wysocki [this message]

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=200910102330.33297.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@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