linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Kalle Valo <kvalo@codeaurora.org>
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:50:48 +0200	[thread overview]
Message-ID: <57b89f3bd6db01fa84f59c1e07f919853af636fe.camel@coelho.fi> (raw)
In-Reply-To: <87lg32jta2.fsf@kamboji.qca.qualcomm.com>

On Wed, 2019-01-30 at 13:09 +0200, Kalle Valo wrote:
> 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?

Ugh, I broke something when resolving conflicts.  I'll send a fix asap.

--
Luca.


  reply	other threads:[~2019-01-30 11:50 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 [this message]
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=57b89f3bd6db01fa84f59c1e07f919853af636fe.camel@coelho.fi \
    --to=luca@coelho.fi \
    --cc=david.e.box@intel.com \
    --cc=joe.konno@intel.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxwifi@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).