From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Broadcom Linux <bcm43xx-dev@berlios.de>
Subject: Re: [PATCH 1/4] create cfg80211
Date: Tue, 13 Feb 2007 01:15:31 +0100 [thread overview]
Message-ID: <200702130115.32118.mb@bu3sch.de> (raw)
In-Reply-To: <1171267928.4881.9.camel@johannes.berg>
On Monday 12 February 2007 09:12, Johannes Berg wrote:
> The real bug I'm chasing (use-after-free leading to oops when rmmod'ing
> bcm43xx-d80211 while device is up) is in bcm43xx-d80211 and I found it
> too. Consider the following changes I made to debug:
Should be fixed in my tree now.
Thanks for the good bugreport.
--
Greetings Michael.
next prev parent reply other threads:[~2007-02-13 0:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 16:27 [PATCH 0/4] cfg80211 johannes
2007-02-09 16:27 ` [PATCH 1/4] create cfg80211 johannes
2007-02-11 19:39 ` Johannes Berg
2007-02-12 8:12 ` Johannes Berg
2007-02-13 0:15 ` Michael Buesch [this message]
2007-02-09 16:27 ` [PATCH 3/4] cfg80211: wext compat code johannes
2007-02-13 15:42 ` Johannes Berg
2007-02-09 16:27 ` [PATCH 4/4] wext: clean up johannes
2007-02-09 16:33 ` [PATCH 0/4] cfg80211 Johannes Berg
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=200702130115.32118.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@berlios.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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.