From: Surya Prabhakar N <surya.prabhakar@wipro.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: caglar@pardus.org.tr, linux-kernel@vger.kernel.org,
kkeil@suse.de, kai.germaschewski@gmx.de,
isdn4linux@listserv.isdn4linux.de,
akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/12] drivers/isdn/hisax/avm_pci.c: replace pci_find_device with pci_get_device
Date: Sun, 15 Jul 2007 15:41:49 +0530 [thread overview]
Message-ID: <1184494309.18254.16.camel@bluegenie> (raw)
In-Reply-To: <4699CF56.7010304@garzik.org>
On Sun, 2007-07-15 at 03:40 -0400, Jeff Garzik wrote:
> To be more clear, your solution is incorrect unless the pci_dev_put()
> occurs after the last reference to hw.{elsa,diva,hfc,njet,...}.dev,
> which is where the HiSax ISDN drivers store their reference to struct
> pci_dev during the runtime life of the PCI device.
>
> Am I missing where your patch does this?
It is really missing :-(
>
> By way of further interest, a few hours _before_ (yes, really) I saw
> your patches, I resumed converting the ISDN HiSax PCI drivers to use the
> PCI driver API. You can find this work in
> git://git.kernel.org/.../jgarzik/misc-2.6.git#isdn-pci.
>
> If you fix your patches' lifetime problems, I will ACK them myself,
> since my effort is a spare time effort. But just wanted you to be aware
> that I am deep into the code you are fixing, and can at least speak
> somewhat knowledgeably on the specific lines of code you are changing.
I can see the bug. Thanks for updating me. I really missed the point
that these whole set of drivers are a part of hisax.ko...
most of the initialization is done in hisax/config.c
Now are you suggesting that we should have a pci_dev_put in config.c
where you have the module_exit.
I am not sure where I can call the dev_put.
consider hisax/avm_pci.c
in which if we have a code like the below
dev_avm = pci_get_device(PCI_VENDOR_ID_AVM,
PCI_DEVICE_ID_AVM_A1, dev_avm))) {
dev_avm is getting initialized in this file
static struct pci_dev *dev_avm __devinitdata = NULL;
so can I do an
extern static struct pci_dev *dev_avm;
in the config.c
and call pci_dev_put(dev_avm) in config.c file's module_exit or
whereever there is an error return?
>
> Jeff
>
>
>
-surya.
prev parent reply other threads:[~2007-07-15 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 22:44 S.Çağlar Onur
2007-07-15 0:40 ` Jeff Garzik
[not found] ` <A94AD757879CE142B7CEBC3E6FF5D3EC015DAC49@BLR-EC-MBX02.wipro.com>
2007-07-15 4:59 ` Jeff Garzik
2007-07-15 7:40 ` Jeff Garzik
2007-07-15 10:11 ` Surya Prabhakar N [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=1184494309.18254.16.camel@bluegenie \
--to=surya.prabhakar@wipro.com \
--cc=akpm@linux-foundation.org \
--cc=caglar@pardus.org.tr \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=jeff@garzik.org \
--cc=kai.germaschewski@gmx.de \
--cc=kkeil@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®