From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH] cfg80211: no cookies in cfg80211_send_ABCD()
Date: Thu, 15 Oct 2009 08:54:49 +0200 [thread overview]
Message-ID: <200910150854.49914.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <20091014200837.GA11962@tuxdriver.com>
> This doesn't appear to be any different (other than the
> subject) than the previous version?
Right, but VGERs simple spam filter prevented the first version
to go to the mailing-list. He didn't like the triple-X in
cfg80211_send_XXX() in the subject ...
next prev parent reply other threads:[~2009-10-15 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 7:06 [PATCH] cfg80211: no cookies in cfg80211_send_ABCD() Holger Schurig
2009-10-14 20:08 ` John W. Linville
2009-10-15 6:54 ` Holger Schurig [this message]
2009-10-15 13:02 ` John W. Linville
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=200910150854.49914.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--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).