From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/3] mac80211: include ieee80211_local in chanctx
Date: Mon, 10 Mar 2014 22:27:46 +0200 [thread overview]
Message-ID: <1394483266.30155.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1394191196-6425-2-git-send-email-michal.kazior@tieto.com> (sfid-20140307_122524_327332_7B691FCF)
On Fri, 2014-03-07 at 12:19 +0100, Michal Kazior wrote:
> Channel contexts are implicitly bound to hw
> already so make it possible to dereference it
> through the channel context itself.
>
> This will make it possible to reduce number of
> arguments for chanctx-related functions.
I don't really see much point in this, is there ever anything where we
really get only a channel context and don't already have the local
pointer?
With interfaces, at least, we need it because we can get an interface
through e.g. do_stop or do_open, so we don't have an easy way to
reference local, but here? I don't think our functions have so many
arguments that it's worth putting a pointer into the struct instead.
johannes
next prev parent reply other threads:[~2014-03-10 20:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 11:19 [PATCH 1/3] mac80211: fix racy usage of chanctx->refcount Michal Kazior
2014-03-07 11:19 ` [PATCH 2/3] mac80211: include ieee80211_local in chanctx Michal Kazior
2014-03-10 20:27 ` Johannes Berg [this message]
2014-03-11 7:36 ` Michal Kazior
2014-03-07 11:19 ` [PATCH 3/3] mac80211: compute chanctx refcount dynamically Michal Kazior
2014-03-07 14:44 ` Johannes Berg
2014-03-08 4:34 ` Zhao, Gang
2014-03-09 9:47 ` Eliad Peller
2014-03-09 15:15 ` Eliad Peller
2014-03-11 7:46 ` Michal Kazior
2014-03-11 13:16 ` Johannes Berg
2014-03-11 13:33 ` Michal Kazior
2014-03-19 14:05 ` Johannes Berg
2014-03-09 9:40 ` [PATCH 1/3] mac80211: fix racy usage of chanctx->refcount Eliad Peller
2014-03-10 20:29 ` 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=1394483266.30155.1.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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).