From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Geliang Tang <geliangtang@163.com>,
<linux-wireless@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: drop unlikely behind WARN_ON()
Date: Mon, 5 Oct 2015 14:23:18 +0300 [thread overview]
Message-ID: <87si5p4l09.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1444027933.1875.0.camel@sipsolutions.net> (Johannes Berg's message of "Mon, 5 Oct 2015 08:52:13 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> The subject is entirely wrong - this is not a cfg80211 patch.
Yes, please use prefix "ath6kl: ".
--
Kalle Valo
next prev parent reply other threads:[~2015-10-05 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 7:09 [PATCH] cfg80211: drop unlikely behind WARN_ON() Geliang Tang
2015-10-05 6:52 ` Johannes Berg
2015-10-05 11:23 ` Kalle Valo [this message]
2015-10-05 12:46 ` [PATCH v2] ath6kl: " Geliang Tang
2015-10-09 8:49 ` Kalle Valo
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=87si5p4l09.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=geliangtang@163.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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 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).