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-03-22
Date: Sat, 30 Mar 2019 08:36:35 +0200 [thread overview]
Message-ID: <87ftr43m30.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <c1c92313e0ecec1110d60d5624e94c8d75d5e664.camel@coelho.fi> (Luca Coelho's message of "Fri, 22 Mar 2019 12:58:10 +0200")
Luca Coelho <luca@coelho.fi> writes:
> Hi Kalle,
>
> This is the first batch of fixes for v5.1. 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 7dfc45e6282a7662279d168cc1219929456f8750:
>
> mt76x02: do not enable RTS/CTS by default (2019-03-19 17:37:25 +0200)
>
> 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-03-22
>
> for you to fetch changes up to 972d8e1377795556024e948357e82532890f2f7d:
>
> iwlwifi: add new 0x2723/0x2080 card for 22000 (2019-03-22 12:49:05 +0200)
>
> ----------------------------------------------------------------
> First batch of iwlwifi fixes intended for v5.1
>
> * add some new PCI IDs (plus a struct name change they depend on);
> * fix crypto with new devices, namely 22560 and above;
> * a bunch of fixes (and a dependency) for the new debugging infra;
>
> ----------------------------------------------------------------
Pulled, thanks Luca.
--
Kalle Valo
prev parent reply other threads:[~2019-03-30 6:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 10:58 pull-request: iwlwifi-fixes 2019-03-22 Luca Coelho
2019-03-30 6:36 ` 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=87ftr43m30.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).