From: Arjan van de Ven <arjan@infradead.org>
To: Kristen Accardi <kristen.c.accardi@intel.com>
Cc: pcihpd-discuss@lists.sourceforge.net, greg@kroah.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch] pciehp: dont call pci_enable_dev
Date: Tue, 25 Apr 2006 08:16:59 +0200 [thread overview]
Message-ID: <1145945819.3114.0.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1145919059.6478.29.camel@whizzy>
On Mon, 2006-04-24 at 15:50 -0700, Kristen Accardi wrote:
> Don't call pci_enable_device from pciehp because the pcie port service driver
> already does this.
hmmmm shouldn't pci_enable_device on a previously enabled device just
succeed? Sounds more than logical to me to make it that way at least...
next prev parent reply other threads:[~2006-04-25 6:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 22:50 Kristen Accardi
2006-04-25 6:16 ` Arjan van de Ven [this message]
2006-04-25 22:00 ` Kristen Accardi
2006-04-26 6:04 ` [Pcihpd-discuss] " Rolf Eike Beer
2006-04-26 15:52 ` Arjan van de Ven
2006-04-26 16:32 ` Kristen Accardi
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=1145945819.3114.0.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®