All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 0/5] ath10k: making static variables const
Date: Wed, 24 Apr 2013 14:18:00 +0300	[thread overview]
Message-ID: <87haiw6utz.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20130424063524.20002.20647.stgit@localhost6.localdomain6> (Kalle Valo's message of "Wed, 24 Apr 2013 09:36:34 +0300")

Kalle Valo <kvalo@qca.qualcomm.com> writes:

> Did some review of static variables and noticed that
> we had quite a few variables which were not const.
>
> Please review carefully, I might have missed something.
>
> ---
>
> Kalle Valo (5):
>       ath10k: make rx_legacy_rate_idx variable const
>       ath10k: make host_ce_config_wlan static variable const
>       ath10k: make target_ce_config_wlan and target_service_to_ce_map_wlan const
>       ath10k: make iee80211 iface combination structures static
>       ath10k: copy ieee80211_supported_band for each instance

Applied.

-- 
Kalle Valo

      parent reply	other threads:[~2013-04-24 11:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24  6:36 [ath9k-devel] [PATCH 0/5] ath10k: making static variables const Kalle Valo
2013-04-24  6:36 ` [ath9k-devel] [PATCH 1/5] ath10k: make rx_legacy_rate_idx variable const Kalle Valo
2013-04-24  6:36 ` [ath9k-devel] [PATCH 2/5] ath10k: make host_ce_config_wlan static " Kalle Valo
2013-04-24  6:36 ` [ath9k-devel] [PATCH 3/5] ath10k: make target_ce_config_wlan and target_service_to_ce_map_wlan const Kalle Valo
2013-04-24  6:37 ` [ath9k-devel] [PATCH 4/5] ath10k: make iee80211 iface combination structures static Kalle Valo
2013-04-24  7:39   ` Michal Kazior
2013-04-24 10:25     ` Kalle Valo
2013-04-24  6:37 ` [ath9k-devel] [PATCH 5/5] ath10k: copy ieee80211_supported_band for each instance Kalle Valo
2013-04-24 11:18 ` Kalle Valo [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=87haiw6utz.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.