From: Luca Coelho <luca@coelho.fi>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: iwlwifi-next 2021-08-26
Date: Sun, 29 Aug 2021 19:15:59 +0300 [thread overview]
Message-ID: <e048218dbe3338124ba09908cb1e49ec89214a96.camel@coelho.fi> (raw)
In-Reply-To: <87wno44i8k.fsf@codeaurora.org>
On Sun, 2021-08-29 at 14:12 +0300, Kalle Valo wrote:
> Luca Coelho <luca@coelho.fi> writes:
>
> > Hi Kalle,
> >
> > Here's my pull request for v5.15 with all the patchesets I sent
> > earlier. This is all normal development, new features, bugfixes and
> > cleanups. 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 e3f30ab28ac866256169153157f466d90f44f122:
> >
> > Merge branch 'pktgen-samples-next' (2021-08-25 13:44:30 +0100)
> >
> > 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-2021-08-26
> >
> > for you to fetch changes up to d9a406ac813dd6a4cfc92bc2576adf43219792ef:
> >
> > iwlwifi: bump FW API to 66 for AX devices (2021-08-26 23:39:05 +0300)
> >
> > ----------------------------------------------------------------
> > iwlwifi patches for v5.15
> >
> > * Support scanning hidden 6GHz networks;
> > * Some improvements in the FW error dumps;
> > * Add some HE capability flags
> > * A bunch of janitorial clean-ups;
> > * Clean-ups in the TX code;
> > * Small fix for SMPS;
> > * Support for a new hardware family (Bz);
> > * Small fix in the scan code;
> > * A bunch of changes in the D3 code, including new FW API;
> > * Finalize the refactoring of 6GHz scan;
> > * Initial changes in the SAR profile code;
> > * Fix reading one of our ACPI tables (WTAS);
> > * Support some new ACPI table revisions;
> > * Support new API of the WoWlan status FW notification;
> > * Fixes in SAR ACPI tables handling;
> > * Some debugging improvements;
> > * Fix in ROC;
> > * Support for new FW API versions;
> > * Support new FW command versions;
> > * Ongoing work on support for Bz devices;
> > * Add new DHC framework to help with debugging of FW flows;
> > * Some other small fixes, clean-ups and improvements.
> >
> > ----------------------------------------------------------------
>
> I'm not convinced about CONFIG_IWLWIFI_DHC option yet, that needs more
> discussion.
Okay, so just let me know what the issue is (now that we depend on
EXPERT) and let's decide what to do with it.
> As the merge window most likely starts today, and I didn't want to
> unnecessarily delay rest of iwlwifi patches, I decided to pull from a
> commit before that DHC stuff:
>
> git pull git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next.git e257d969f36503b8eb1240f32653a1afb3109f86
>
> So pulled, thanks.
Thanks for pulling! But we also need at least the top patch in my pull-
req, the one that bumps the FW API...
--
Cheers,
Luca.
next prev parent reply other threads:[~2021-08-29 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 20:47 pull-request: iwlwifi-next 2021-08-26 Luca Coelho
2021-08-29 11:12 ` Kalle Valo
2021-08-29 16:15 ` Luca Coelho [this message]
2021-09-01 6:16 ` Kalle Valo
2021-09-01 7:16 ` Luca Coelho
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=e048218dbe3338124ba09908cb1e49ec89214a96.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
/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