linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org, Luca Coelho <luciano.coelho@intel.com>
Subject: Re: [PATCH] iwlwifi: mvm: fix merge damage in iwl_mvm_rx_mpdu_mq()
Date: Thu, 31 Jan 2019 13:34:48 +0000 (UTC)	[thread overview]
Message-ID: <20190131133448.AB603605FC@smtp.codeaurora.org> (raw)
In-Reply-To: <20190130123811.26839-1-luca@coelho.fi>

Luca Coelho <luca@coelho.fi> wrote:

> From: Luca Coelho <luciano.coelho@intel.com>
> 
> A call to iwl_mvm_add_rtap_sniffer_config() was missing due to a merge
> damage when I submitted the patch mentioned below.  And this causes
> the following compilation warning:
> 
> drivers/net/wireless/intel/iwlwifi/mvm/rxmq.c:195:13: warning: 'iwl_mvm_add_rtap_sniffer_config' defined but not used [-Wunused-function]
>  static void iwl_mvm_add_rtap_sniffer_config(struct iwl_mvm *mvm,
>              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> Fix it by adding the if block that calls this function.
> 
> Fixes: 9bf13bee2d74 ("iwlwifi: mvm: include configured sniffer AID in radiotap")
> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>

Patch applied to wireless-drivers-next.git, thanks.

3864be551405 iwlwifi: mvm: fix merge damage in iwl_mvm_rx_mpdu_mq()

-- 
https://patchwork.kernel.org/patch/10788503/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


      reply	other threads:[~2019-01-31 13:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 14:19 pull-request: iwlwifi-next 2019-01-29 Luca Coelho
2019-01-30 11:09 ` Kalle Valo
2019-01-30 11:50   ` Luca Coelho
2019-01-30 12:38     ` [PATCH] iwlwifi: mvm: fix merge damage in iwl_mvm_rx_mpdu_mq() Luca Coelho
2019-01-31 13:34       ` 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=20190131133448.AB603605FC@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luca@coelho.fi \
    --cc=luciano.coelho@intel.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).