From: Johannes Berg <johannes@sipsolutions.net>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 1/5] cfg80211/mac80211: DFS setup chandef for cac event
Date: Wed, 06 Nov 2013 13:20:20 +0100 [thread overview]
Message-ID: <1383740420.14307.42.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CALhHN=pxo00fg6KYHJbw34FEP8k-6aiT2CMb5y7oRyVOyTzFZA@mail.gmail.com> (sfid-20131106_131026_149690_597A3878)
On Wed, 2013-11-06 at 13:10 +0100, Janusz Dziedzic wrote:
> On 6 November 2013 11:09, Johannes Berg <johannes@sipsolutions.net> wrote:
> > On Tue, 2013-11-05 at 14:48 +0100, Janusz Dziedzic wrote:
> >
> >> void cfg80211_cac_event(struct net_device *netdev,
> >> + struct cfg80211_chan_def *chandef,
> >
> > Jouni had a patch to make a lot of these pointers const - this one
> > probably should be as well.
> >
>
> Yes.
> I can send this one after Jouni patch will be merged.
Well I don't think he even sent it yet, so you could just send this one
with const?
johannes
prev parent reply other threads:[~2013-11-06 12:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 13:48 [PATCH v2 1/5] cfg80211/mac80211: DFS setup chandef for cac event Janusz Dziedzic
2013-11-05 13:48 ` [PATCH v2 2/5] mac80211: DFS setup chandef for radar_event correctly Janusz Dziedzic
2013-11-06 10:09 ` Johannes Berg
2013-11-05 13:48 ` [PATCH v2 3/5] cfg80211: add helper functions for start/end freq Janusz Dziedzic
2013-11-05 13:48 ` [PATCH v2 4/5] cfg80211: DFS check chandef usable before CAC Janusz Dziedzic
2013-11-06 10:12 ` Johannes Berg
2013-11-05 13:48 ` [PATCH v2 5/5] cfg80211: allow beaconing after DFS CAC Janusz Dziedzic
2013-11-06 10:11 ` Johannes Berg
2013-11-06 12:08 ` Janusz Dziedzic
2013-11-06 10:09 ` [PATCH v2 1/5] cfg80211/mac80211: DFS setup chandef for cac event Johannes Berg
2013-11-06 12:10 ` Janusz Dziedzic
2013-11-06 12:20 ` 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=1383740420.14307.42.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=janusz.dziedzic@tieto.com \
--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).