From: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH] acpiphp: fix use of list_for_each macro
Date: Mon, 30 Oct 2006 11:37:15 -0800 [thread overview]
Message-ID: <20061030113715.b5e8ddec.kristen.c.accardi@intel.com> (raw)
In-Reply-To: <20061028183943.GA9973@localhost>
On Sun, 29 Oct 2006 03:39:43 +0900
Akinobu Mita <akinobu.mita@gmail.com> wrote:
> This patch fixes invalid usage of list_for_each()
>
> list_for_each (node, &bridge_list) {
> bridge = (struct acpiphp_bridge *)node;
> ...
> }
>
> This code works while the member of list node is located at the
> head of struct acpiphp_bridge.
>
> Cc: Greg Kroah-Hartman <gregkh@suse.de>
> Cc: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
Acked-by: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
>
> drivers/pci/hotplug/acpiphp_glue.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> Index: work-fault-inject/drivers/pci/hotplug/acpiphp_glue.c
> ===================================================================
> --- work-fault-inject.orig/drivers/pci/hotplug/acpiphp_glue.c
> +++ work-fault-inject/drivers/pci/hotplug/acpiphp_glue.c
> @@ -1693,14 +1693,10 @@ void __exit acpiphp_glue_exit(void)
> */
> int __init acpiphp_get_num_slots(void)
> {
> - struct list_head *node;
> struct acpiphp_bridge *bridge;
> - int num_slots;
> -
> - num_slots = 0;
> + int num_slots = 0;
>
> - list_for_each (node, &bridge_list) {
> - bridge = (struct acpiphp_bridge *)node;
> + list_for_each_entry (bridge, &bridge_list, list) {
> dbg("Bus %04x:%02x has %d slot%s\n",
> pci_domain_nr(bridge->pci_bus),
> bridge->pci_bus->number, bridge->nr_slots,
prev parent reply other threads:[~2006-10-30 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 18:39 Akinobu Mita
2006-10-30 19:37 ` Kristen Carlson Accardi [this message]
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=20061030113715.b5e8ddec.kristen.c.accardi@intel.com \
--to=kristen.c.accardi@intel.com \
--cc=akinobu.mita@gmail.com \
--cc=gregkh@suse.de \
--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
all inboxes | Powered by JetHome®