public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nils Faerber <nils@kernelconcepts.de>,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH] Watchdog: i8xx_tco remove pci_find_device
Date: Wed, 19 Jul 2006 11:08:06 +0159	[thread overview]
Message-ID: <44BDF68D.9040104@gmail.com> (raw)
In-Reply-To: <20060719061154.GA2438@infomag.infomag.iguana.be>

Wim Van Sebroeck napsal(a):
> Hi Jiri,

Hi Wim.

> 
> Just back from a small holiday, but:
> 
>> Watchdog: i8xx_tco remove pci_find_device.
>>
>> Use refcounting for pci device obtaining. Use PCI_DEVICE macro.
>>
>> Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
> 
> Why the pci_dev_put's? We aren't registering the PCI devices. See
> the comment above the MODULE_DEVICE_TABLE:
> /*
>  * Data for PCI driver interface
>  *
>  * This data only exists for exporting the supported
>  * PCI ids via MODULE_DEVICE_TABLE.  We do not actually
>  * register a pci_driver, because someone else might one day
>  * want to register another driver on the same PCI id.
>  */

Sure, but it's not registering, but telling the subsystem, we use the device, so
that user can't hotunplug it since some driver uses it and reads and writes its
registers. It's purpose of refcounting in pci_dev_{put,get}() (pci_dev_get is
called in pci_get_device()).

> Since the I/O controller Hub has several functions we explicitely
> do not register the PCI device...
> 
> PS: In the -mm tree there is allready a replacement for this driver...
> Plan is to get this one into linus tree soon.

This patch is against 2.6.18-rc1-mm2. (Maybe you mean there are some patches
coming to -rc2-mm1?)

thanks,
-- 
<a href="http://www.fi.muni.cz/~xslaby/">Jiri Slaby</a>
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

  reply	other threads:[~2006-07-19  9:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060719002225.85BFC201A1@srebbe.iguana.be>
2006-07-19  6:11 ` [PATCH] Watchdog: i8xx_tco remove pci_find_device Wim Van Sebroeck
2006-07-19  9:09   ` Jiri Slaby [this message]
2006-07-19 19:58     ` Wim Van Sebroeck

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=44BDF68D.9040104@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nils@kernelconcepts.de \
    --cc=wim@iguana.be \
    /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