From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Jeff Garzik <jeff@garzik.org>
Cc: oakad@yahoo.com, Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/{mmc,misc}: handle PCI errors on resume
Date: Fri, 13 Oct 2006 09:00:35 +0100 [thread overview]
Message-ID: <20061013080035.GD28654@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20061011214809.GA21756@havoc.gtf.org>
On Wed, Oct 11, 2006 at 05:48:09PM -0400, Jeff Garzik wrote:
> Since pci_enable_device() is one of the first things called in the
> resume step, take the minimalist approach and return immediately, if
> pci_enable_device() fails during resume.
NAK, for the same reason as for drivers/serial.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-10-13 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 21:48 [PATCH] drivers/{mmc,misc}: handle PCI errors on resume Jeff Garzik
2006-10-13 8:00 ` Russell King [this message]
2006-10-21 10:24 ` Pierre Ossman
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=20061013080035.GD28654@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oakad@yahoo.com \
/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