public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: MUNEDA Takahiro <muneda.takahiro@jp.fujitsu.com>
Cc: pavel@ucw.cz, kristen.c.accardi@intel.com,
	pcihpd-discuss@lists.sourceforge.net, linux-acpi@vger.kernel.org,
	len.brown@intel.com
Subject: Re: [PATCH 0/7] acpiphp - slots management fix
Date: Thu, 26 Jan 2006 20:14:25 -0800	[thread overview]
Message-ID: <20060127041425.GA20453@kroah.com> (raw)
In-Reply-To: <87acdrp5y9.wl%muneda.takahiro@jp.fujitsu.com>

On Fri, Jan 20, 2006 at 07:08:30PM +0900, MUNEDA Takahiro wrote:
> Hi,
> 
> This series of patches contains slots management fix.
> Here are summary of changes:
> 
> o [PATCH 1/7] - removes unnecesary struct members
> 
> o [PATCH 2/7] - removes init_slots(), because acpiphp doesn't
>                 register slots when driver is loaded.
> 
> o [PATCH 3/7] - changes register_slot() to register hotplug
>                 slots when they are found
> 
> o [PATCH 4/7] - changes init_bridge_misc() to register hotplug
>                 slots when they are found
> 
> o [PATCH 5/7] - removes cleanup_slots(), because acpiphp
>                 doesn't unregister slots when driver is going
>                 to be un-loaded.
> 
> o [PATCH 6/7] - changes cleanup_brige() to unregister hotplug
>                 slots when acpiphp cleanup the bridge.
> 
> o [PATCH 7/7] - adds spin_lock/_unlock to protect slot_list
> 
> 
> For more specifc information, please see the header of each patch.
> These patches are against 2.6.16-rc1. I tested them on Tiger4.

This patch series does not even compile when applied:

  CC [M]  drivers/pci/hotplug/acpiphp_core.o
drivers/pci/hotplug/acpiphp_core.c: In function `acpiphp_register_hotplug_slot':
drivers/pci/hotplug/acpiphp_core.c:355: error: `hotplug_slot' undeclared (first use in this function)
drivers/pci/hotplug/acpiphp_core.c:355: error: (Each undeclared identifier is reported only once
drivers/pci/hotplug/acpiphp_core.c:355: error: for each function it appears in.)
drivers/pci/hotplug/acpiphp_core.c:359: error: `hotplug_slot_info' undeclared (first use in this function)
make[2]: *** [drivers/pci/hotplug/acpiphp_core.o] Error 1

Care to redo them?

thanks,

greg k-h

  parent reply	other threads:[~2006-01-27  4:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20 10:08 [PATCH 0/7] acpiphp - slots management fix MUNEDA Takahiro
2006-01-20 11:30 ` Pavel Machek
2006-01-23  0:37   ` [Pcihpd-discuss] " MUNEDA Takahiro
2006-01-27  4:14 ` Greg KH [this message]
2006-01-29  3:34   ` MUNEDA Takahiro
2006-01-29  3:45     ` Greg KH
2006-01-31 18:20       ` Kristen Accardi
2006-02-07 20:13         ` Greg KH
2006-02-10 19:28           ` Kristen Accardi
2006-02-13  2:27             ` MUNEDA Takahiro
2006-02-14  7:13               ` [PATCH] acpiphp - slot management fix - V2 MUNEDA Takahiro
2006-02-14  9:17                 ` [Pcihpd-discuss] " Kenji Kaneshige
2006-02-15  9:26                   ` [PATCH] acpiphp - slot management fix - V3 MUNEDA Takahiro

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=20060127041425.GA20453@kroah.com \
    --to=greg@kroah.com \
    --cc=kristen.c.accardi@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=muneda.takahiro@jp.fujitsu.com \
    --cc=pavel@ucw.cz \
    --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