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: <20070211210258.0b8da53c@localhost.localdomain>
Date:	Sun, 11 Feb 2007 21:02:58 +0000
From:	Alan <alan@...rguk.ukuu.org.uk>
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?

> > "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 ?

And testing/submitting drivers, perhaps with additional text in that to
make it clear we want suspend/resume support or good excuses

"Please verify your driver correctly handles suspend and resume. If it
does not your patch submission is likely to be suspended and only resume
when the driver correctly handles this feature"


-
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/