From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: unregister ml groups on failure
Date: Tue, 24 Feb 2009 17:53:42 -0800 [thread overview]
Message-ID: <20090225015342.GB22710@tesla> (raw)
In-Reply-To: <1235526282.28635.0.camel@johannes.local>
On Tue, Feb 24, 2009 at 05:44:42PM -0800, Johannes Berg wrote:
> On Tue, 2009-02-24 at 17:14 -0800, Luis R. Rodriguez wrote:
> > We were not doing so before.
>
> and we don't need to, they get removed with the family automatically.
Oh, nice, I figured that was a chance but thought it would have been too
good to be true.
Luis
prev parent reply other threads:[~2009-02-25 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 1:14 [PATCH] cfg80211: unregister ml groups on failure Luis R. Rodriguez
2009-02-25 1:44 ` Johannes Berg
2009-02-25 1:53 ` Luis R. Rodriguez [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=20090225015342.GB22710@tesla \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).