From: Borislav Petkov <bp@alien8.de>
To: "Lucas C. Villa Real" <lucasvr@gobolinux.org>, Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org,
Wey-Yi Guya <wey-yi.w.guy@intel.com>,
Johannes Berg <johannes.berg@intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Pekka Enberg <penberg@kernel.org>
Subject: Re: [PATCH] Initialize pointer on request_firmware
Date: Tue, 27 Sep 2011 22:13:58 +0200 [thread overview]
Message-ID: <20110927201358.GB4249@liondog.tnic> (raw)
In-Reply-To: <CAAvzgtZf2pFcKmAvccH4oJuiUJaugWbX1gwng7CK9B2DwN3ocA@mail.gmail.com>
On Fri, Sep 23, 2011 at 12:51:36PM -0300, Lucas C. Villa Real wrote:
> On Thu, Sep 22, 2011 at 4:05 PM, Lucas C. Villa Real
> <lucasvr@gobolinux.org> wrote:
> > On Thu, Sep 22, 2011 at 3:20 PM, Borislav Petkov <bp@alien8.de> wrote:
> >> On Thu, Sep 22, 2011 at 11:03:27AM -0700, Greg KH wrote:
> >>> The patch was in the 2.6.36 kernel, so by nature of that, 3.0 will also
> >>> have it, right?
> >>
> >> Ok, a colleague of mine gave me 3.0.4 to stare at - and you're right
> >> the patch is there. So what is still missing is caca9510ff4e5 from
> >> upstream which reroutes the exit path so that firmware_p is NULLed
> >> before returning -EBUSY.
> >>
> >> Lucas, can you apply caca9510ff4e5 from upstream and verify it fixes the
> >> issue for ya?
> >
> > Sure. I'll do that tonight and will let you now -- the laptop I'm
> > using right now doesn't suffer from that problem.
>
> caca9510ff4e5 fixes it. Thanks for the pointer!
Looks like the ball is with Greg now :-).
Thanks.
--
Regards/Gruss,
Boris.
prev parent reply other threads:[~2011-09-27 20:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 2:55 Lucas C. Villa Real
2011-09-22 9:23 ` Borislav Petkov
2011-09-22 17:18 ` Greg KH
2011-09-22 17:54 ` Borislav Petkov
2011-09-22 18:03 ` Greg KH
2011-09-22 18:20 ` Borislav Petkov
2011-09-22 19:05 ` Lucas C. Villa Real
2011-09-23 15:51 ` Lucas C. Villa Real
2011-09-27 20:13 ` Borislav Petkov [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=20110927201358.GB4249@liondog.tnic \
--to=bp@alien8.de \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@suse.de \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucasvr@gobolinux.org \
--cc=penberg@kernel.org \
--cc=wey-yi.w.guy@intel.com \
/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®