From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: fix wiphy remove if no regulatory request
Date: Mon, 01 Dec 2008 20:34:48 +0100 [thread overview]
Message-ID: <1228160089.10627.35.camel@johannes.berg> (raw)
In-Reply-To: <43e72e890812011101r3ad8225aofafdada8b5699535@mail.gmail.com> (sfid-20081201_200153_742533_C8FF06C8)
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
On Mon, 2008-12-01 at 11:01 -0800, Luis R. Rodriguez wrote:
> On Mon, Dec 1, 2008 at 3:07 AM, Johannes Berg <johannes@sipsolutions.net> wrote:
> > Fixes the segfault I just pointed out.
>
> Thanks, the commit log should include the panic I guess though right?
Maybe, maybe not, it's fairly clear what's going on from the diff, I
think.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2008-12-01 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 11:07 [PATCH] cfg80211: fix wiphy remove if no regulatory request Johannes Berg
2008-12-01 19:01 ` Luis R. Rodriguez
2008-12-01 19:34 ` Johannes Berg [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=1228160089.10627.35.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.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