From: "Michał Kazior" <michal.kazior@tieto.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 04/12] mac80211: prepare ieee80211_get_tx_channel_type to per-vif
Date: Fri, 23 Mar 2012 15:05:10 +0100 [thread overview]
Message-ID: <4F6C8316.5080600@tieto.com> (raw)
In-Reply-To: <1332491869.3506.2.camel@jlt3.sipsolutions.net>
Johannes Berg wrote:
>
>> enum nl80211_channel_type ieee80211_get_tx_channel_type(
>> - struct ieee80211_local *local,
>> + struct ieee80211_sub_if_data *sdata,
>> enum nl80211_channel_type channel_type)
>
> I have pending patches to delete this :)
>
You mean you have patches that remove the ieee80211_get_tx_channel_type
function? Are they accessible publicly or do you have them in your local
repository? Do you mind sharing them or are you going to push them soon?
-- Pozdrawiam / Best Regards, Michal Kazior.
next prev parent reply other threads:[~2012-03-23 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 9:22 [RFC 04/12] mac80211: prepare ieee80211_get_tx_channel_type to per-vif Michal Kazior
2012-03-23 8:37 ` Johannes Berg
2012-03-23 14:05 ` Michał Kazior [this message]
2012-03-23 14:10 ` 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=4F6C8316.5080600@tieto.com \
--to=michal.kazior@tieto.com \
--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 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).