From: trem <trem@zarb.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] drivers/char/mxser.c : replace pci_find_device by
Date: Sat, 27 May 2006 20:33:30 +0000 [thread overview]
Message-ID: <4478B79A.4080400@zarb.org> (raw)
In-Reply-To: <4478AF44.3040701@yahoo.fr>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
Nish Aravamudan wrote:
> On 5/27/06, trem <tremyfr@yahoo.fr> wrote:
>> From: trem <tremyfr@yahoo.fr>
>>
>> This patch simply change pci_find_device by pci_get_device, because
>> pci_find_device is deprecated. pci_dev_put has been added after the
>> loop to decrement the counter if necessary.
>
> Can't the pci_dev_put() be unconditional? pci_dev_put() does the
> checking for NULL itself, it would seem. There are two cases that are
> (logicall, not practically, possible):
>
> 1) We don't even enter the while loop, which can only occur if someone
> alters mxser_pcibrds[]. In this case, we'll call pci_dev_put(pdev),
> pdev == NULL, and return from the call immediately.
>
> 2) We need to clean-up the last iteration of the loop. In this case
> pci_dev_put(pdev) will do the right thing.
>
> Thanks,
> Nish
>
Hi
you're right pci_dev_put check if the parameter is NULL, so checking it
before
is useless. It just avoid to call the function.
I send a new patch
trem
[-- Attachment #2: mxser_replace_pci_find_device_by_pci_get_device.patch --]
[-- Type: text/x-patch, Size: 585 bytes --]
diff --git a/drivers/char/mxser.c b/drivers/char/mxser.c
index 0fb2fb9..28298dc 100644
--- a/drivers/char/mxser.c
+++ b/drivers/char/mxser.c
@@ -817,7 +817,7 @@ static int mxser_init(void)
index = 0;
b = 0;
while (b < n) {
- pdev = pci_find_device(mxser_pcibrds[b].vendor, mxser_pcibrds[b].device, pdev);
+ pdev = pci_get_device(mxser_pcibrds[b].vendor, mxser_pcibrds[b].device, pdev);
if (pdev == NULL) {
b++;
continue;
@@ -854,6 +854,7 @@ static int mxser_init(void)
m++;
}
}
+ pci_dev_put(pdev);
#endif
retval = tty_register_driver(mxvar_sdriver);
[-- Attachment #3: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2006-05-27 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 19:57 [KJ] [PATCH] drivers/char/mxser.c : replace pci_find_device by trem
2006-05-27 20:09 ` Nish Aravamudan
2006-05-27 20:33 ` trem [this message]
2006-05-29 21:32 ` Greg KH
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=4478B79A.4080400@zarb.org \
--to=trem@zarb.org \
--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.