public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Kristen Accardi <kristen.c.accardi@intel.com>
To: Greg KH <greg@kroah.com>
Cc: MUNEDA Takahiro <muneda.takahiro@jp.fujitsu.com>,
	pavel@ucw.cz, pcihpd-discuss@lists.sourceforge.net,
	linux-acpi@vger.kernel.org, len.brown@intel.com
Subject: Re: [Pcihpd-discuss] Re: [PATCH 0/7] acpiphp - slots management fix
Date: Tue, 31 Jan 2006 10:20:18 -0800	[thread overview]
Message-ID: <1138731618.18768.5.camel@whizzy> (raw)
In-Reply-To: <20060129034502.GA7168@kroah.com>

On Sat, 2006-01-28 at 19:45 -0800, Greg KH wrote:
> On Sun, Jan 29, 2006 at 12:34:29PM +0900, MUNEDA Takahiro wrote:
> > Hi,
> > 
> > At Thu, 26 Jan 2006 20:14:25 -0800,
> > Greg KH <greg@kroah.com> wrote:
> > > 
> > > 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?
> > 
> > 
> > I'm sorry for my late replying.
> > And thanks for your taking care of my patch.
> > 
> > At first, please let me introduce the base idea of this patch.
> > I'm trying to support p2p bridge hotplug with acpiphp.
> > 
> >  Current acpiphp manages hotplug slot by ID. The ID is incremented
> >  when acpiphp founds hotpluggable slots.
> >  If the bridges(with hotpluggable slots) are hotplugged many times,
> >  the hotpluggable slots are added many times also. The ID might be
> >  overflowed. So this patch removes IDs to manage slots.
> > 
> >  And, this patch changes the slot register/unregister timing.
> >  Current acpiphp registers the slots in the init_slots()
> >  called from acpiphp_init(), and unregisters the slots in the
> >  cleanup_slots() called from acpiphp_exit().
> >  acpiphp doesn't assume the increase and decrease of the
> >  hotpluggable slots.
> >  This patch removes the slot register/unregister processes from the
> >  init/exit phases. Instead, adds the these processes in the bridge
> >  add/cleanup phases.
> > 
> > Currently, this change doesn't have any meanings. But these changes
> > are needed to support p2p bridge(with hotplug slot) hotplug.
> > 
> > Here is an updated patch. Old patches were not need to be separated,
> > so I merge them into below patch.
> > 
> > This patch is against 2.6.16-rc1-mm3. I tested them on Tiger4 and
> > it works fine.
> 
> Ok, Kristen, have any objections to this patch?  I know it's in much the
> same area that you are working in.
> 
> thanks,
> 
> greg k-h
> -

Just reviewing them, they seem like they will be fine to me.

Thanks,
Kristen



  reply	other threads:[~2006-01-31 18:16 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
2006-01-29  3:34   ` [Pcihpd-discuss] " MUNEDA Takahiro
2006-01-29  3:45     ` Greg KH
2006-01-31 18:20       ` Kristen Accardi [this message]
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=1138731618.18768.5.camel@whizzy \
    --to=kristen.c.accardi@intel.com \
    --cc=greg@kroah.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