linux-kernel - Re: NAK new drivers without proper power management?

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <45CF96D0.8070004@imap.cc>
Date:	Sun, 11 Feb 2007 23:21:04 +0100
From:	Tilman Schmidt <tilman@...p.cc>
To:	Pavel Machek <pavel@....cz>
CC:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Arjan van de Ven <arjan@...radead.org>,
	nigel@...el.suspend2.net, LKML <linux-kernel@...r.kernel.org>
Subject: Re: NAK new drivers without proper power management?

Am 11.02.2007 20:42 schrieb Pavel Machek:
[...]
>> What about this:
>>
>> "If the device requires that, implement .suspend and .resume or at least
>> define .suspend that will always return -ENOSYS (then people will know they
>> have to unload the driver before the suspend).  Similarly, if you aren't sure
>> whether or not the device requires .suspend and .resume, define .suspend that
>> will always return -ENOSYS."
> 
> Sounds ok to me. Where should this text go?
> Documentation/SubmittingDrivers ?


Documentation/power/devices.txt?

-- 
Tilman Schmidt                          E-Mail: tilman@...p.cc
Bonn, Germany
- In theory, there is no difference between theory and practice.
  In practice, there is.


Download attachment "signature.asc" of type "application/pgp-signature" (254 bytes)