public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Greg KH <gregkh@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-pci@atrey.karlin.mff.cuni.cz,
	Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH 3/3] pci: gt96100eth use pci probing
Date: Thu, 25 May 2006 12:31:32 +0159	[thread overview]
Message-ID: <4475879B.6030003@gmail.com> (raw)
In-Reply-To: <44758683.4070205@garzik.org>

Jeff Garzik napsal(a):
> Jiri Slaby wrote:
>>>> +unprobe:
>>>> +    for (j = i; j > 0; j--) {
>>>> +        struct gt96100_if_t *gtif = &gtifs[j - 1];
>>>> +        gt96100_remove1(gtif);
>>>> +    }
>>>> +    kfree(gtifs);
>>> upon failure, you fail to set drvdata back to NULL
>> What is the purpose of setting this to NULL, other drivers don't do
>> that too?
> 
> A simple grep(1) shows well over 300 cases that do this.
But also shows the latter case: some of them do not have pci_dev_setdrv([^,]*,
NULL) -- it finds only one occurence of that function (that set the value).
> 
> And it's just logical:  don't leave a pointer hanging around, after it
> has been kfree'd.
Seems logical. Will do it.

thanks,
-- 
Jiri Slaby         www.fi.muni.cz/~xslaby
\_.-^-._   jirislaby@gmail.com   _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E

  reply	other threads:[~2006-05-25 10:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060525003151.598EAC7C19@atrey.karlin.mff.cuni.cz>
2006-05-25  0:52 ` [PATCH 3/3] pci: gt96100eth use pci probing Jeff Garzik
2006-05-25 10:13   ` Jiri Slaby
2006-05-25 10:17     ` Jiri Slaby
2006-05-25 10:20       ` Jeff Garzik
2006-05-25 10:35         ` Jiri Slaby
2006-05-25 10:27     ` Jeff Garzik
2006-05-25 10:32       ` Jiri Slaby [this message]
2006-05-25 10:35         ` Jeff Garzik
2006-05-25 10:31     ` Jiri Slaby
2006-05-25 10:41   ` Ralf Baechle
2006-05-25 20:36     ` Jiri Slaby

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=4475879B.6030003@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=gregkh@suse.de \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=ralf@linux-mips.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