lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2549404.ZIjrAGNJPJ@vostro.rjw.lan>
Date:	Sat, 29 Nov 2014 01:50:12 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Ulf Hansson <ulf.hansson@...aro.org>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Linux PM list <linux-pm@...r.kernel.org>,
	Linux PCI <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Kevin Hilman <khilman@...nel.org>
Subject: Re: [PATCH 0/4] PM: Use CONFIG_PM instead of CONFIG_PM_RUNTIME in core code

On Thursday, November 27, 2014 11:34:03 PM Ulf Hansson wrote:
> [...]
> 
> > That said whether or not it is ever useful to set PM_RUNTIME alone is a good
> > question.  In my opinion it is useful today, at least on some platforms that
> > don't really support system suspend or hibernation in any form.  However, it
> > may not be the case any more when suspend-to-idle becomes mature enough,
> > because that should just work for any platform without any kind of special
> > support.  We're still missing some timekeeping bits there, but once that
> > gap has been covered, we may just eliminate PM_SLEEP as well if there's a
> > broad consensus on that.
> 
> That's sounds like a good approach, thanks for sharing your ideas and plans.
> 
> Feel free to add my reviewed-by tag to this patchset as well.

I'll do that, thanks!

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ