From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Robert Hancock <hancockr@shaw.ca>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Pavel Machek <pavel@ucw.cz>, Jeff Garzik <jeff@garzik.org>,
Daniel Barkalow <barkalow@iabervon.org>,
pm list <linux-pm@lists.osdl.org>, Willy Tarreau <w@1wt.eu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: NAK new drivers without proper power management?
Date: Mon, 12 Feb 2007 10:06:06 +1100 [thread overview]
Message-ID: <1171235166.4493.100.camel@nigel.suspend2.net> (raw)
In-Reply-To: <200702111953.02229.rjw@sisk.pl>
Hi.
On Sun, 2007-02-11 at 19:53 +0100, Rafael J. Wysocki wrote:
> > Having drivers explicitly marked as to whether they are safe is a good kernel
> > feature; what to do if they're not is policy.
>
> That's true, but I assume that the people who opt for doing that are also
> willing to take part in the review of the drivers. :-)
Absolutely :)
> Well, I don't think so. Let's estimate the number of drivers that define
> .resume() right now:
>
> $ grep -I -l -r '.resume =' linux-2.6.20/drivers/ | wc
> 102 102 4169
I think the '.resume =' doesn't help - some have tabs. I ran '\.resume'
and got 351.
It would be interesting to see how many struct pci_driver etc instances
lack resume methods.
Regards,
Nige
next prev parent reply other threads:[~2007-02-11 23:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.xSKPgY66Q+DPCZ1pszFFfdrJ0To@ifi.uio.no>
[not found] ` <45CD24F6.8090107@shaw.ca>
[not found] ` <1171076554.10170.5.camel@nigel.suspend2.net>
2007-02-10 9:34 ` [PATCH] Re: NAK new drivers without proper power management? Rafael J. Wysocki
2007-02-10 10:02 ` Nigel Cunningham
2007-02-10 10:30 ` Rafael J. Wysocki
2007-02-10 17:52 ` Daniel Barkalow
2007-02-10 19:50 ` Rafael J. Wysocki
2007-02-11 6:54 ` Willy Tarreau
2007-02-11 12:13 ` Matthew Garrett
2007-02-11 13:09 ` Willy Tarreau
2007-02-11 13:19 ` Matthew Garrett
2007-02-11 13:37 ` Willy Tarreau
2007-02-11 13:50 ` Rafael J. Wysocki
2007-02-11 13:57 ` Willy Tarreau
2007-02-11 14:36 ` Rafael J. Wysocki
2007-02-11 15:19 ` Pekka Enberg
2007-02-11 18:31 ` Rafael J. Wysocki
2007-02-11 17:27 ` Daniel Barkalow
2007-02-11 18:53 ` Rafael J. Wysocki
2007-02-11 23:06 ` Nigel Cunningham [this message]
2007-02-11 23:10 ` Rafael J. Wysocki
2007-02-11 21:04 ` Stefan Richter
2007-02-11 21:10 ` Pavel Machek
2007-02-11 17:36 ` Robert Hancock
2007-02-11 22:49 ` Nigel Cunningham
2007-02-11 19:37 ` Pavel Machek
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=1171235166.4493.100.camel@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=barkalow@iabervon.org \
--cc=hancockr@shaw.ca \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=mjg59@srcf.ucam.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=w@1wt.eu \
/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