public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Greg KH <greg@kroah.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add hook for PCI resource deallocation
Date: Tue, 21 Sep 2004 10:35:12 +0900	[thread overview]
Message-ID: <414F8550.6020209@jp.fujitsu.com> (raw)
In-Reply-To: <20040917214943.GE14340@kroah.com>

Greg KH wrote:
> On Thu, Sep 16, 2004 at 09:54:14PM +0900, Kenji Kaneshige wrote:
>> Hi,
>> 
>> This patch adds a hook 'pcibios_disable_device()' into
>> pci_disable_device() to call architecture specific PCI resource
>> deallocation code. It's a opposite part of pcibios_enable_device().
>> We need this hook to deallocate architecture specific PCI resource
>> such as IRQ resource, etc.. This patch is just for adding the hook,
>> so pcibios_disable_device() is defined as a null function on all
>> architecture so far.
> 
> I'd prefer to wait until there was an actual user of this hook before
> adding it to the kernel.  Otherwise someone (likely me) will notice this
> hook in a few days and go, "hey, no one is using this, let's clean it
> up" :)
> 
> So, how about we wait until you have a patch that needs this before I
> apply it?
> 

Okay.
I'll post a patch that needs this soon.

Thanks,
Kenji Kaneshige


  reply	other threads:[~2004-09-21  1:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 12:54 [PATCH] add hook for PCI resource deallocation Kenji Kaneshige
2004-09-17 21:49 ` Greg KH
2004-09-21  1:35   ` Kenji Kaneshige [this message]
2004-09-24  0:49   ` Kenji Kaneshige
2004-09-24 20:02 ` Ashok Raj
2004-09-24 21:22   ` Greg KH
2004-09-27  8:06     ` Kenji Kaneshige
2004-09-28 22:00       ` Greg KH
2004-09-29  0:55         ` Kenji Kaneshige
2004-09-30 21:50       ` Andrew Morton
2004-09-30 22:21         ` Ashok Raj
2004-09-30 23:03           ` Andrew Morton
2004-10-01  2:11             ` Kenji Kaneshige

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=414F8550.6020209@jp.fujitsu.com \
    --to=kaneshige.kenji@jp.fujitsu.com \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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