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 2017-10-06
Date: Tue, 10 Oct 2017 08:56:10 +0300 [thread overview]
Message-ID: <87r2ub4kcl.fsf@codeaurora.org> (raw)
In-Reply-To: <1507288582.908.127.camel@coelho.fi> (Luca Coelho's message of "Fri, 06 Oct 2017 14:16:22 +0300")
Luca Coelho <luca@coelho.fi> writes:
> Here is the second set of fixes for 4.14. More details in the tag
> description.
>
> I have sent this out before and kbuildbot didn't find any issues.
> Please let me know if there are any issues.
>
> Cheers,
> Luca.
>
>
> The following changes since commit c503dd38f850be28867ef7a42d9abe5ade81a9bd:
>
> brcmsmac: make some local variables 'static const' to reduce stack size (2017-10-02 16:52:55 +0300)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git tags/iwlwifi-for-kalle-2017-10-06
>
> for you to fetch changes up to 44fd09dad5d2b78efbabbbbf623774e561e36cca:
>
> iwlwifi: nvm: set the correct offsets to 3168 series (2017-10-06 13:59:44 +0300)
>
> ----------------------------------------------------------------
> Second set of iwlwifi fixes for 4.14
>
> * Fix support for 3168 device series;
> * Fix a potential crash when using FW debugging recording;
> * Improve channel flags parsing to avoid warnings on too long traces;
> * Return -ENODATA when the temperature is not available, since the
> -EIO we were returning was causing fatal errors in userspace;
> * Avoid printing too many messages in dmesg when using monitor mode,
> since this can become very noisy and completely flood the logs;
>
> ----------------------------------------------------------------
Pulled, thanks.
Actually I pulled this already yesterday but forgot to reply.
--
Kalle Valo
prev parent reply other threads:[~2017-10-10 5:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 11:16 pull-request: iwlwifi 2017-10-06 Luca Coelho
2017-10-10 5:56 ` 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=87r2ub4kcl.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 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).