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-fixes 2019-04-28
Date: Sun, 28 Apr 2019 14:27:39 +0300 [thread overview]
Message-ID: <87mukas72s.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <aab3d1cab0caf00d7c3ae1cc10ca3ec99cc54efd.camel@coelho.fi> (Luca Coelho's message of "Sun, 28 Apr 2019 10:06:50 +0300")
Luca Coelho <luca@coelho.fi> writes:
> This is the fourth batch of fixes for v5.1. It contains two fixes I
> send in the last patchset plus a patch that I sent separately to fix a
> merge damage caused by the previous pull. 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 b82d6c1f8f8288f744a9dcc16cd3085d535decca:
>
> mwifiex: Make resume actually do something useful again on SDIO cards (2019-04-25 14:05:14 +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-2019-04-28
>
> for you to fetch changes up to d156e67d3f58c5d3c7ebe1bec80657db534f32d4:
>
> iwlwifi: mvm: fix merge damage in iwl_mvm_vif_dbgfs_register() (2019-04-28 09:59:59 +0300)
>
> ----------------------------------------------------------------
> Fourth batch of patches intended for v5.1
>
> * Fix an oops when we receive a packet with bogus lengths;
> * Fix a bug that prevented 5350 devices from working;
> * Fix a small merge damage from the previous series;
>
> ----------------------------------------------------------------
Pulled, thanks Luca.
--
Kalle Valo
prev parent reply other threads:[~2019-04-28 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 7:06 pull-request: iwlwifi-fixes 2019-04-28 Luca Coelho
2019-04-28 11:27 ` 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=87mukas72s.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).