From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org, linuxwifi@intel.com,
david.e.box@intel.com, joe.konno@intel.com
Subject: Re: pull-request: iwlwifi-next 2019-01-29
Date: Wed, 30 Jan 2019 13:09:57 +0200 [thread overview]
Message-ID: <87lg32jta2.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <7e68c48a5c59b164a28d434765b03cba6243c12f.camel@coelho.fi> (Luca Coelho's message of "Tue, 29 Jan 2019 16:19:01 +0200")
Luca Coelho <luca@coelho.fi> writes:
> This is the second batch of patches intended for v5.1. This includes
> the last two patchsets I sent. Usual development work. More details
> about the contents in the tag description.
>
> I have sent this out before and kbuildbot reported success.
>
> Please let me know if there are any issues.
>
> Cheers,
> Luca.
>
>
> The following changes since commit 64e2330580fbbfa7077ef2f608555f07e0bb4956:
>
> Merge tag 'iwlwifi-next-for-kalle-2019-01-25' of git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next (2019-01-29 14:56:05 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next.git tags/iwlwifi-next-for-kalle-2019-01-29
>
> for you to fetch changes up to 01f377dc927da6e42cbffb00fc8d431c8341da3f:
>
> iwiwifi: fix bad monitor buffer register addresses (2019-01-29 16:10:33 +0200)
>
> ----------------------------------------------------------------
> Second batch of iwlwifi patches intended for v5.1
>
> * A bunch of fixes for issues found with static analyzers;
> * Relicense the pcie submodule to dual GPL/BSD;
> * Reworked the TOF/CSI implementation;
> * Work on new debugging infra continues;
> * Some product name updates in the human-readable strings
> * Some more cleanups for the device configuration refactoring;
> * General bugfixes;
> * Other cleanups and small fixes;
>
> ----------------------------------------------------------------
Pulled, thanks.
Oh, but I see a new 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,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Can you send separately a patch to fix this so that I can apply it
directly?
--
Kalle Valo
next prev parent reply other threads:[~2019-01-30 11:10 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 [this message]
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
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=87lg32jta2.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=david.e.box@intel.com \
--cc=joe.konno@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luca@coelho.fi \
/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).