From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org, linuxwifi@intel.com
Subject: Re: pull-request: iwlwifi-next 2020-03-17
Date: Wed, 18 Mar 2020 14:06:35 +0200 [thread overview]
Message-ID: <87sgi5kgtw.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <9940614e4051cc054569033ca7c127f3339469e6.camel@coelho.fi> (Luca Coelho's message of "Tue, 17 Mar 2020 21:26:16 +0200")
Luca Coelho <luca@coelho.fi> writes:
> Here's the fist batch of patches intended for v5.7. This includes
> the last patchset I sent out. Usual development work. More details
> about the contents in the tag description.
>
> Please let me know if there are any issues.
>
> Cheers,
> Luca.
>
>
> The following changes since commit 377c0a94ad1cf005c47d7a502d1f8e46fbcf747a:
>
> Merge ath-next from git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git (2020-03-16 07:29:55 +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-2020-03-17
>
> for you to fetch changes up to 5e003982b07ae351cadef4c252b3279b3424bf0d:
>
> iwlwifi: move AX200 devices to the new table (2020-03-17 21:10:47 +0200)
>
> ----------------------------------------------------------------
> First set of iwlwifi patches intended for v5.7
>
> * Refactoring of the device selection algorithms;
>
> ----------------------------------------------------------------
Pulled, thanks Luca.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-03-18 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 19:26 pull-request: iwlwifi-next 2020-03-17 Luca Coelho
2020-03-18 12:06 ` 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=87sgi5kgtw.fsf@kamboji.qca.qualcomm.com \
--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).