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 2018-11-11
Date: Thu, 15 Nov 2018 17:00:42 +0200 [thread overview]
Message-ID: <874lci9yhx.fsf@codeaurora.org> (raw)
In-Reply-To: <fa556d1212cd48befec5fe0ea8a1f9ca2efcae89.camel@coelho.fi> (Luca Coelho's message of "Sun, 11 Nov 2018 11:12:55 +0200")
Luca Coelho <luca@coelho.fi> writes:
> This is the first batch of patches intended for v4.21. This includes
> only the last patchset I sent. Usual development work, new PCI IDs and
> small fixes and cleanups. 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 bb38177cb6c6dc973ad8b88f219742b29f3002f1:
>
> Merge ath-next from git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git (2018-11-09 17:15:25 +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-2018-11-11
>
> for you to fetch changes up to 56b657f7f9c07421a4f910b7e2b382184f1ddbc8:
>
> iwlwifi: fw: use helper to determine whether to dump paging (2018-11-11 11:06:23 +0200)
>
> ----------------------------------------------------------------
> First set of iwlwifi patches for 4.21
>
> * PCI IDs for some new 9000-series cards;
> * Improve antenna usage on connection problems;
> * Some improvements in the debugging code;
> * Other clean-ups and small fixes;
>
> ----------------------------------------------------------------
Pulled, thanks.
--
Kalle Valo
prev parent reply other threads:[~2018-11-15 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 9:12 pull-request: iwlwifi-next 2018-11-11 Luca Coelho
2018-11-15 15:00 ` 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=874lci9yhx.fsf@codeaurora.org \
--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).