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-11-13-3
Date: Fri, 15 Nov 2019 09:49:41 +0200 [thread overview]
Message-ID: <871ru9o9yi.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <12f1628d715bd9915b291aebe8512cfb3c44dec8.camel@coelho.fi> (Luca Coelho's message of "Fri, 15 Nov 2019 09:43:55 +0200")
Luca Coelho <luca@coelho.fi> writes:
> Hi Kalle,
>
> Here's another updated pull request with the second batch of patches
> intended for v5.4. This includes the last patchset 2 patchsets I sent.
> Usual development work. More details about the contents in the tag
> description.
>
> In this update I have fixed the Change-Id tags that slipped in. Sorry
> about that.
>
> I pushed these patches to my pending branch when I sent them out and
> kbuildbot reported success.
>
> Please let me know if there are any issues.
>
> Cheers,
> Luca.
>
>
> The following changes since commit 21c60a28af58d7c376502c26fbb0064b39c32917:
>
> rtw88: signal completion even on firmware-request failure (2019-11-08 10:27:03 +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-11-13-3
>
> for you to fetch changes up to 37a8f748bb679ed614878dae9bbdb1cfcf9eb99e:
>
> iwlwifi: mvm: fix non-ACPI function (2019-11-15 09:37:36 +0200)
>
> ----------------------------------------------------------------
> Second batch of patches intended for v5.5
>
> * Update scan FW API;
> * Fix single antenna diversity support;
> * Bump the supported FW API version;
> * Add debug dump collection on assert in WoWLAN;
> * Fix VHT capabilities settings;
> * Move ACPI handling code fully into acpi.c;
> * Increase the CTDP budget to improve signal strength;
> * A fix for compilation with no ACPI enabled;
> * Enable adaptive dwell on P2P interfaces;
>
> ----------------------------------------------------------------
Our emails crossed, and I had already manually fixed (and applied) this
based on v2. So dropping v3.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2019-11-15 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 7:43 pull-request: iwlwifi-next 2019-11-13-3 Luca Coelho
2019-11-15 7:49 ` 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=871ru9o9yi.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).