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 2020-01-11
Date: Sun, 26 Jan 2020 12:10:59 +0200 [thread overview]
Message-ID: <871rrmede4.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <f548bee28a2ef4700a024e33c02b62893af498c7.camel@coelho.fi> (Luca Coelho's message of "Sat, 11 Jan 2020 11:51:28 +0200")
Luca Coelho <luca@coelho.fi> writes:
> Here's the fist batch of patches intended for v5.6. This includes
> the last two patchsets I sent out. Usual development work. More
> details about the contents in the tag description.
>
> I pushed these patches to my pending branch, but it was just now, so I
> didn't get the results from kbuildbot yet.
>
> Please let me know if there are any issues.
>
> Cheers,
> Luca.
>
>
> The following changes since commit ae0a723c4cfd89dad31ce238f47ccfbe81b35b84:
>
> Merge ath-next from git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git (2019-12-19 18:27:36 +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-01-11
>
> for you to fetch changes up to 0b295a1eb81f37dc7d4f4f2ee9ef375fb36ab5d8:
>
> iwlwifi: add device name to device_info (2020-01-04 12:48:41 +0200)
>
> ----------------------------------------------------------------
> First set of patches intended for v5.6
>
> * Support new versions of the FTM FW APIs;
> * Fix an old bug in D3 (WoWLAN);
> * A couple of fixes/improvements in the receive-buffers code;
> * Fix in the debugging where we were skipping one TXQ;
> * Support new version of the beacon template FW API;
> * Print some extra information when the driver is loaded;
> * Some debugging infrastructure (aka. yoyo) updates;
> * Support for a new HW version;
> * Second phase of device configuration work started;
> * Some clean-ups;
>
> ----------------------------------------------------------------
Pulled, thanks Luca.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-01-26 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 9:51 pull-request: iwlwifi-next 2020-01-11 Luca Coelho
2020-01-24 14:39 ` Kalle Valo
2020-01-24 14:45 ` Kalle Valo
2020-01-24 18:59 ` Luca Coelho
2020-01-26 10:10 ` 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=871rrmede4.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.