From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org, linuxwifi <linuxwifi@intel.com>
Subject: Re: pull-request: iwlwifi-next 2017-02-06
Date: Tue, 07 Feb 2017 09:32:55 +0200 [thread overview]
Message-ID: <87tw8678wo.fsf@codeaurora.org> (raw)
In-Reply-To: <1486402642.26003.141.camel@coelho.fi> (Luca Coelho's message of "Mon, 06 Feb 2017 19:37:22 +0200")
Luca Coelho <luca@coelho.fi> writes:
> Here's my second pull-request intended for v4.11. Just the usual set of
> fixes, cleanups and improvements, together with the continued work on
> support for new hardware. A bit more details in the tag description.
>
> I have sent this out before and kbuildbot didn't find any issues. I
> have also removed my favorite mistakes, namely the "commit" after the
> Fixes tag. ;)
>
> Please let me know if there are any issues.
>
> Cheers,
> Luca.
>
>
> The following changes since commit 36401cb7ffae731295a6dd1ce2b40d7ad74245f4:
>
> brcmfmac: be more verbose when PSM's watchdog fires (2017-02-02 08:14:26 +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-2017-02-06
>
> for you to fetch changes up to 8364fbb497f00de21d6d347194fa8b6bbae1d6f5:
>
> iwlwifi: mvm: support new beacon template command (2017-02-06 19:19:27 +0200)
>
> ----------------------------------------------------------------
> Second batch of improvements and fixes for v4.11.
>
> * A bunch of bugfixes for the DQA code;
> * Work on support for new A000 devices continues;
> * Some clean-ups and general improvements
>
> ----------------------------------------------------------------
Pulled, thanks.
--
Kalle Valo
prev parent reply other threads:[~2017-02-07 7:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 17:37 pull-request: iwlwifi-next 2017-02-06 Luca Coelho
2017-02-07 7:32 ` 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=87tw8678wo.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--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 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.