From: Matthieu Baerts <matttbe@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [GIT PULL] wireless-2025-11-05: manual merge
Date: Thu, 6 Nov 2025 13:37:38 +0100 [thread overview]
Message-ID: <fe1a6f17-e26e-4414-8880-3f3137470849@kernel.org> (raw)
In-Reply-To: <11cece9f7e36c12efd732baa5718239b1bf8c950.camel@sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
Hi Johannes,
On 06/11/2025 10:03, Johannes Berg wrote:
> Unrelated to that: I forgot to mention that there's a conflict now
> between net and net-next, which had been reported before between ath and
> ath-next and then wireless and wireless-next, but it's just a simple
> variable addition overlap:
>
> https://lore.kernel.org/all/20251030113037.1932c6d2@canb.auug.org.au/
Thank you for the pointer!
Just in case someone else has this conflict, you can use the rr-cache
files from:
https://github.com/multipath-tcp/mptcp-upstream-rr-cache/commit/56cf8ff
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
[-- Attachment #2: cb34617c2d3ea4f78cfc0768bc4c8d1f00754f00.patch --]
[-- Type: text/x-patch, Size: 538 bytes --]
diff --cc drivers/net/wireless/ath/ath12k/mac.c
index 0348601ecc50,db351c922018..9333225ceef3
--- a/drivers/net/wireless/ath/ath12k/mac.c
+++ b/drivers/net/wireless/ath/ath12k/mac.c
@@@ -4423,7 -4209,7 +4404,8 @@@ static void ath12k_mac_bss_info_changed
{
struct ath12k_vif *ahvif = arvif->ahvif;
struct ieee80211_vif *vif = ath12k_ahvif_to_vif(ahvif);
+ struct ieee80211_vif_cfg *vif_cfg = &vif->cfg;
+ struct ath12k_link_vif *tx_arvif;
struct cfg80211_chan_def def;
u32 param_id, param_value;
enum nl80211_band band;
next prev parent reply other threads:[~2025-11-06 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 15:27 [GIT PULL] wireless-2025-11-05 Johannes Berg
2025-11-06 2:08 ` Jakub Kicinski
2025-11-06 9:03 ` Johannes Berg
2025-11-06 12:37 ` Matthieu Baerts [this message]
2025-11-06 2:10 ` patchwork-bot+netdevbpf
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=fe1a6f17-e26e-4414-8880-3f3137470849@kernel.org \
--to=matttbe@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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.