Linux-Next discussions
 help / color / mirror / Atom feed
From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>
Subject: Linux-next conflict between ath-current and ath-next
Date: Mon, 14 Sep 2026 18:40:56 -0700	[thread overview]
Message-ID: <dd5f82ce-90a5-4427-bcdb-656d899c63c2@oss.qualcomm.com> (raw)

For linux-next, wireless, and netdev maintainers:

In drivers/net/wireless/ath/ath12k/wifi7/ahb.c function
ath12k_wifi7_ahb_probe() there is a conflict between:

ce9d5197d651 wifi: ath12k: ahb: Revert undocumented ABI and dead code
in the ath.git ath-current branch

and:

c3bace8584ca wifi: ath12k: add support to load shared firmware on multiPD
in the ath.git ath-next branch

The conflict exists because a new line is added next to ones that were
reverted:
	ab_ahb->scm_auth_enabled = desc->auth_enabled;
 +	ab_ahb->supports_multipd = desc->supports_multipd;
-	ab_ahb->userpd_id = ath12k_wifi7_ahb_get_userpd_id(ab);
+	ab_ahb->userpd_id = ATH12K_AHB_USERPD_ID_0;
	if (!ab_ahb->userpd_id)
		return -EOPNOTSUPP;

Since multi-PD is not completely supported in ath/main, my resolution is to
keep just the ath-current code:
	ab_ahb->scm_auth_enabled = desc->auth_enabled;
	ab_ahb->userpd_id = ATH12K_AHB_USERPD_ID_0;
	if (!ab_ahb->userpd_id)
		return -EOPNOTSUPP;

A DT-approved mechanism for determining UserPD IDs is needed for ath-next.

I'm about to send my ath-current PR to Johannes for v7.3-rc4.

/jeff

                 reply	other threads:[~2026-09-15  1:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=dd5f82ce-90a5-4427-bcdb-656d899c63c2@oss.qualcomm.com \
    --to=jeff.johnson@oss.qualcomm.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=linux-next@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox