All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ashok Raj <ashok.raj@intel.com>
Cc: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add hook for PCI resource deallocation
Date: Fri, 24 Sep 2004 14:22:08 -0700	[thread overview]
Message-ID: <20040924212208.GD7619@kroah.com> (raw)
In-Reply-To: <20040924130251.A26271@unix-os.sc.intel.com>

On Fri, Sep 24, 2004 at 01:02:52PM -0700, Ashok Raj wrote:
> On Thu, Sep 16, 2004 at 05:54:14AM -0700, 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 tested this patch on i386, x86_64 and ia64. But it has not been
> >    tested on other architectures because I don't have these machines.
> > 
> >    Signed-off-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
> > 
> 
> Hi Kenji
> 
> I think instead of modifying all the arch specific code, you could use the __attribute__(weak)
> and define a default dummy funcion in 	drivers/pci/pci.c
> 
> void __attribute__((weak)) pcibios_disable_device(struct pci_dev *dev)	{ }
> 
> 
> each arch that really needs this can define the override function.
> That way you dont need to put the dummy function in several places,
> containing your changes to a very few set of files.

Ohhh, nice.  I like that option better.  Kenji, care to respin your
patches based on this change?

thanks,

greg k-h

  reply	other threads:[~2004-09-24 21:24 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
2004-09-24  0:49   ` Kenji Kaneshige
2004-09-24 20:02 ` Ashok Raj
2004-09-24 21:22   ` Greg KH [this message]
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=20040924212208.GD7619@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=ashok.raj@intel.com \
    --cc=kaneshige.kenji@jp.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.