public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Akinobu Mita <akinobu.mita@gmail.com>,
	Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	Len Brown <len.brown@intel.com>
Subject: Re: [PATCH -mm] acpi: use list.h API for sub_driver list
Date: Sun, 29 Oct 2006 13:42:33 +0000	[thread overview]
Message-ID: <20061029134233.GA22902@infradead.org> (raw)
In-Reply-To: <20061029134003.GC10295@localhost>

On Sun, Oct 29, 2006 at 10:40:03PM +0900, Akinobu Mita wrote:
> On Sat, Oct 28, 2006 at 08:02:54PM +0100, Christoph Hellwig wrote:
> > Any chance to just switch the driver to use the list.h APIs instead
> > of opencoding lists?
> 
> Subject: [PATCH -mm] acpi: use list.h API for sub_driver list
> 
> Use the list.h APIs instead of opencoding lists.

Maybe it's just me but I don't see a place where we actually ever
iterate this list.  Len, do you plan to introduce users of the list anytime
soon?  In that case the patch below looks good to me, else we should just
rip it out completely.

> Cc: Len Brown <len.brown@intel.com>
> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
> 
> Index: work-fault-inject/drivers/acpi/pci_root.c
> ===================================================================
> --- work-fault-inject.orig/drivers/acpi/pci_root.c
> +++ work-fault-inject/drivers/acpi/pci_root.c
> @@ -65,17 +65,14 @@ struct acpi_pci_root {
>  
>  static LIST_HEAD(acpi_pci_roots);
>  
> -static struct acpi_pci_driver *sub_driver;
> +static LIST_HEAD(sub_driver);
>  
>  int acpi_pci_register_driver(struct acpi_pci_driver *driver)
>  {
>  	int n = 0;
>  	struct list_head *entry;
>  
> -	struct acpi_pci_driver **pptr = &sub_driver;
> -	while (*pptr)
> -		pptr = &(*pptr)->next;
> -	*pptr = driver;
> +	list_add_tail(&driver->list, &sub_driver);
>  
>  	if (!driver->add)
>  		return 0;
> @@ -96,14 +93,7 @@ void acpi_pci_unregister_driver(struct a
>  {
>  	struct list_head *entry;
>  
> -	struct acpi_pci_driver **pptr = &sub_driver;
> -	while (*pptr) {
> -		if (*pptr == driver)
> -			break;
> -		pptr = &(*pptr)->next;
> -	}
> -	BUG_ON(!*pptr);
> -	*pptr = (*pptr)->next;
> +	list_del(&driver->list);
>  
>  	if (!driver->remove)
>  		return;
> Index: work-fault-inject/include/linux/acpi.h
> ===================================================================
> --- work-fault-inject.orig/include/linux/acpi.h
> +++ work-fault-inject/include/linux/acpi.h
> @@ -480,7 +480,7 @@ void acpi_penalize_isa_irq(int irq, int 
>  void acpi_pci_irq_disable (struct pci_dev *dev);
>  
>  struct acpi_pci_driver {
> -	struct acpi_pci_driver *next;
> +	struct list_head list;
>  	int (*add)(acpi_handle handle);
>  	void (*remove)(acpi_handle handle);
>  };
---end quoted text---

      reply	other threads:[~2006-10-29 13:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-28 18:53 [PATCH] acpi: fix single linked list manipulation Akinobu Mita
2006-10-28 19:02 ` Christoph Hellwig
2006-10-29 13:40   ` [PATCH -mm] acpi: use list.h API for sub_driver list Akinobu Mita
2006-10-29 13:42     ` Christoph Hellwig [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=20061029134233.GA22902@infradead.org \
    --to=hch@infradead.org \
    --cc=akinobu.mita@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --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