All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricardo Martins <ricardo@scarybox.net>
To: kernel-janitors@vger.kernel.org
Subject: Re: warning: ???pci_find_device??? is deprecated
Date: Fri, 02 May 2008 16:42:19 +0000	[thread overview]
Message-ID: <20080502164219.GA6237@macbookpro> (raw)
In-Reply-To: <20080502162539.GG14976@parisc-linux.org>

[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]

On Fri, 02 May 2008 18:28, Julia Lawall wrote:
> On Fri, 2 May 2008, Matthew Wilcox wrote:
> 
> > On Fri, May 02, 2008 at 05:19:40PM +0100, Ricardo Martins wrote:
> > > There are 14 drivers in drivers/isdn/hisax/ still using calls to
> > > pci_find_device() instead of the pci_get_device(). From what I gather, a
> > > simple sed 's|pci_find_device|pci_get_device|' is enough to fix this,
> > > since both functions use the same input and give the same output.
> > > Is this correct?
> >
> > It's never correct.  If it were that easy (a) there wouldn't be a rename
> > in the first place and (b) it would have been done with a shell-script
> > already.
> >
> > pci_get_device increments a refcount on the pci_dev.  pci_find_device
> > does not.  Your patch must include calls to pci_dev_put() *when
> > appropriate*.  Note, for example, that pci_get_device decrements the
> > refcount on the device passed in.
> 
> I looked at this briefly at one point.  To my recollection, many of the
> files that use pci_find_device store the result in a global variable.  So
> one would have to think carefully about the useful lifetime of the value
> of that variable to know where to put the puts.
> 
> julia

I see. Thank you both for shedding some light on this.

-- 
 Ricardo Martins  *  scarybox.net  *  GPG key: 0x1308F1B4

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

      parent reply	other threads:[~2008-05-02 16:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 16:25 warning: ???pci_find_device??? is deprecated Matthew Wilcox
2008-05-02 16:28 ` Julia Lawall
2008-05-02 16:42 ` Ricardo Martins [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=20080502164219.GA6237@macbookpro \
    --to=ricardo@scarybox.net \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.