public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
	gregkh@suse.de, davej@codemonkey.org.uk, arjan@infradead.org,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [GIT PATCH] More PCI patches for 2.6.13
Date: Fri, 09 Sep 2005 21:27:50 -0400	[thread overview]
Message-ID: <43223696.5020902@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0509091644050.30958@g5.osdl.org>

Linus Torvalds wrote:
> 
> On Fri, 9 Sep 2005, Andrew Morton wrote:
> 
>>If something like a PCI power management function fails then it will likely
>>cause suspend or resume to malfunction, and we have a lot of such problems.
> 
> 
> No, for several reasons.
> 
> First off, some of those functions can't fail in normal usage. Thus 
> telling people that they have to check the return code is insane.
> 
> Secondly, at least some of the suspend failures have historically been
> because drivers returned errors for no good reason. Adding yet another 
> broken reason to return error is not going to help.

Agreed.

	Jeff




  reply	other threads:[~2005-09-10  1:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 22:07 [GIT PATCH] More PCI patches for 2.6.13 Greg KH
2005-09-09 22:37 ` Linus Torvalds
2005-09-09 22:54   ` Greg KH
2005-09-09 23:22     ` Linus Torvalds
2005-09-09 23:28       ` Linus Torvalds
2005-09-09 23:36       ` Andrew Morton
2005-09-10  0:22         ` Linus Torvalds
2005-09-10  1:27           ` Jeff Garzik [this message]
2005-09-10 18:33       ` John W. Linville
2005-09-10 18:53         ` Linus Torvalds
2005-09-11 11:33           ` Pavel Machek
2005-09-10 10:05     ` Arjan van de Ven
  -- strict thread matches above, loose matches on Subject: below --
2005-09-10 21:07 Alan Stern
2005-09-10 21:12 ` Linus Torvalds
2005-09-10 21:58   ` Jeff Garzik
2005-09-10 22:31     ` Andrew Morton
2005-09-10 22:53       ` Linus Torvalds
2005-09-10 23:44         ` Jeff Garzik
2005-09-11  0:02           ` Linus Torvalds
2005-09-11  0:17             ` Jeff Garzik
2005-09-11  0:27               ` Linus Torvalds
2005-09-10 23:02       ` Pavel Machek
2005-09-11 11:38       ` Pavel Machek
2005-09-10 22:32     ` Alistair John Strachan
2005-09-10 23:47       ` Jeff Garzik
2005-09-11  6:47         ` David Woodhouse
2005-09-11  4:41       ` Greg KH
2005-09-11  6:47         ` Alistair John Strachan
2005-09-11  2:34 Gabriel A. Devenyi

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=43223696.5020902@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=davej@codemonkey.org.uk \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=torvalds@osdl.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