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-02-22
Date: Sat, 30 Mar 2019 08:40:23 +0200 [thread overview]
Message-ID: <87bm1s3lwo.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <8dc374567ff4a1138b5c9605ecc2dc0aeb9bc4bc.camel@coelho.fi> (Luca Coelho's message of "Fri, 22 Mar 2019 14:16:08 +0200")
Luca Coelho <luca@coelho.fi> writes:
> This is the first batch of patches intended for v5.2. This includes
> the last two patchsets I sent. Usual development work. 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 501faf710230b67e470b314868110357cf3a554d:
>
> Merge ath-next from git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git (2019-02-28 11:50:40 +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-03-22
>
> for you to fetch changes up to fe63f21b20df1adaab90c1839d36ee7c6e4b6ac0:
>
> iwlwifi: dbg_ini: align to FW api version 1 (2019-03-22 12:59:42 +0200)
>
> ----------------------------------------------------------------
> First batch of patches intended for v5.2
>
> * Send NO_DATA events so they can be captured in radiotap;
> * Some channel-switch changes;
> * Support for multiple BSSID;
> * Continued work and bugfixes for the new debugging infra;
> * Support for some new FW API versions;
> * Some work to support new hardware;
> * General bugfixes;
> * Other cleanups;
>
> ----------------------------------------------------------------
Pulled, thanks Luca.
--
Kalle Valo
prev parent reply other threads:[~2019-03-30 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 12:16 pull-request: iwlwifi-next 2019-02-22 Luca Coelho
2019-03-30 6:40 ` 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=87bm1s3lwo.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