From: Jaswinder Singh <jaswinder@infradead.org>
To: David Dillow <dave@thedillows.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [GIT PULL]: firmware patches for building firmware into kernel
Date: Fri, 08 Aug 2008 11:38:46 +0530 [thread overview]
Message-ID: <1218175726.13359.3.camel@jaswinder.satnam> (raw)
In-Reply-To: <1218169537.17642.40.camel@obelisk.thedillows.org>
Hello Dave,
On Fri, 2008-08-08 at 00:25 -0400, David Dillow wrote:
> On Fri, 2008-08-08 at 09:09 +0530, Jaswinder Singh wrote:
> > On Thu, 2008-08-07 at 22:59 -0400, David Dillow wrote:
> > > I don't like releasing the firmware before the pci_unregister_driver()
> > > call. I worry about ordering issues during cleanup, though I'll admit I
> > > have not yet researched if it will be a problem. In any event, if you're
> > > going to request it once per adapter in typhoon_init_one(), then it
> > > should be in the per-device struct, and released in
> > > typhoon_remove_one().
> >
> > Here is updated patch :
>
> You've fixed one part of the issues I described, but I think you've left
> open the possibility of dangling pointers when one card in a multi NIC
> system fails to come up. Again, I need to track down the code to see if
> I'm all wet or not.
>
That's why I introduced firmware_release_all() for buggy drivers.
I think firmware_release_all() is best for you case.
Thank you,
Jaswinder Singh.
next prev parent reply other threads:[~2008-08-08 6:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 16:56 Jaswinder Singh
2008-08-07 17:30 ` David Dillow
2008-08-07 17:34 ` Jaswinder Singh
2008-08-07 18:21 ` David Dillow
2008-08-08 1:38 ` Jaswinder Singh
2008-08-08 2:59 ` David Dillow
2008-08-08 3:39 ` Jaswinder Singh
2008-08-08 4:25 ` David Dillow
2008-08-08 6:08 ` Jaswinder Singh [this message]
2008-08-08 3:31 ` Jaswinder Singh
2008-08-08 4:10 ` David Dillow
2008-08-08 4:33 ` Jaswinder Singh
2008-08-08 12:36 ` David Dillow
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=1218175726.13359.3.camel@jaswinder.satnam \
--to=jaswinder@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dave@thedillows.org \
--cc=dwmw2@infradead.org \
--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®