linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 1/1] powerpc: Export PCI slot reset API
Date: Fri, 26 Jan 2007 03:49:25 +0100	[thread overview]
Message-ID: <20070126024924.GA18537@lst.de> (raw)

On Fri, Jan 12, 2007 at 02:49:32PM -0600, Brian King wrote:
> 
> Adds two new APIs to assert/deassert PCI reset to a given
> device. This is needed for an ipr PCI-E adapter which does not
> properly implement either BIST nor PCI-E hot reset, requiring
> a PCI-E warm reset, which is what this implements.

Having this exported only on a single platform is wrong. Any API
for PCI drivers should be implemented on all platforms, even if
some of it have it stubbed out.

             reply	other threads:[~2007-01-26  2:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-26  2:49 Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-24 22:03 [PATCH 1/1] powerpc: Export PCI slot reset API Brian King
2007-01-12 20:49 Brian King
2007-01-23 23:28 ` Brian King

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=20070126024924.GA18537@lst.de \
    --to=hch@lst.de \
    --cc=brking@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).