linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 2/7] ath10k: implement chanctx API
Date: Fri, 30 Jan 2015 13:58:14 +0100	[thread overview]
Message-ID: <1422622694.1919.17.camel@sipsolutions.net> (raw)
In-Reply-To: <1422621086-28970-3-git-send-email-michal.kazior@tieto.com> (sfid-20150130_133341_121083_F7682B5B)


> +++ b/drivers/net/wireless/ath/ath10k/core.h

> @@ -277,6 +282,7 @@ struct ath10k_vif {
>  	dma_addr_t beacon_paddr;
>  
>  	struct ath10k *ar;
> +	struct ath10k_chanctx *arctx;

you also have vif->chanctx_conf pointer, which you could use

ultimately it's a software architecture decision - personally I wouldn't
want to duplicate all that data and the lists etc. in the driver when
mac80211 has them, but that's just my opinion. :)

johannes



  parent reply	other threads:[~2015-01-30 12:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30  8:41 [PATCH 0/7] ath10k: add multi-channel support Michal Kazior
2015-01-30  8:41 ` [PATCH 1/7] ath10k: allow empty ssid vdev config Michal Kazior
2015-01-30  8:41 ` [PATCH 2/7] ath10k: implement chanctx API Michal Kazior
2015-01-30 10:44   ` Michal Kazior
2015-01-30  8:41 ` [PATCH 3/7] ath10k: implement adaptive qcs command Michal Kazior
2015-01-30  8:41 ` [PATCH 4/7] ath10k: protect ar->arvifs linking with data_lock Michal Kazior
2015-01-30  8:41 ` [PATCH 5/7] ath10k: rework tx queue locking Michal Kazior
2015-01-30  8:41 ` [PATCH 6/7] ath10k: implement tx pause wmi event Michal Kazior
2015-01-30  8:41 ` [PATCH 7/7] ath10k: enable multi-channel on supported devices Michal Kazior
2015-01-30 12:31 ` [PATCH v2 0/7] ath10k: add multi-channel support Michal Kazior
2015-01-30 12:31   ` [PATCH v2 1/7] ath10k: allow empty ssid vdev config Michal Kazior
2015-01-30 12:31   ` [PATCH v2 2/7] ath10k: implement chanctx API Michal Kazior
2015-01-30 12:45     ` Johannes Berg
2015-01-30 13:02       ` Michal Kazior
2015-01-30 13:04         ` Johannes Berg
2015-01-30 13:22           ` Michal Kazior
2015-01-30 13:31             ` Johannes Berg
2015-01-30 13:47               ` Michal Kazior
2015-01-30 14:06                 ` Johannes Berg
2015-01-30 12:58     ` Johannes Berg [this message]
2015-01-30 13:06       ` Michal Kazior
2015-01-30 13:10         ` Johannes Berg
2015-01-30 14:01           ` Michal Kazior
2015-01-30 14:10             ` Johannes Berg
2015-01-30 12:31   ` [PATCH v2 3/7] ath10k: implement adaptive qcs command Michal Kazior
2015-01-30 12:31   ` [PATCH v2 4/7] ath10k: protect ar->arvifs linking with data_lock Michal Kazior
2015-01-30 12:31   ` [PATCH v2 5/7] ath10k: rework tx queue locking Michal Kazior
2015-01-30 12:31   ` [PATCH v2 6/7] ath10k: implement tx pause wmi event Michal Kazior
2015-01-30 12:31   ` [PATCH v2 7/7] ath10k: enable multi-channel on supported devices Michal Kazior

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=1422622694.1919.17.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ath10k@lists.infradead.org \
    --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).