From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Kalle Valo <kvalo@kernel.org>, Jeff Johnson <jjohnson@kernel.org>
Cc: Aditya Kumar Singh <aditya.kumar.singh@oss.qualcomm.com>,
Ath10k List <ath10k@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Maharaja Kennadyrajan <maharaja.kennadyrajan@oss.qualcomm.com>,
Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
Subject: Re: linux-next: manual merge of the ath-next tree with the ath tree
Date: Wed, 29 Oct 2025 18:14:55 -0700 [thread overview]
Message-ID: <83c8504d-3159-4a87-a1ea-0fef46bf6762@oss.qualcomm.com> (raw)
In-Reply-To: <20251030113037.1932c6d2@canb.auug.org.au>
On 10/29/2025 5:30 PM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the ath-next tree got a conflict in:
>
> drivers/net/wireless/ath/ath12k/mac.c
>
> between commit:
>
> 9222582ec524 ("Revert "wifi: ath12k: Fix missing station power save configuration"")
>
> from the ath tree and commit:
>
> 6917e268c433 ("wifi: ath12k: Defer vdev bring-up until CSA finalize to avoid stale beacon")
>
> from the ath-next tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
Thanks, Stephen
That resolution matches the text I've prepared for my upcoming pull request:
Note to maintainers:
There is a trivial conflict between two patches:
In ath/ath-current:
9222582ec524 ("Revert "wifi: ath12k: Fix missing station power save configuration"")
In ath/ath-next:
6917e268c433 ("wifi: ath12k: Defer vdev bring-up until CSA finalize to avoid stale beacon")
The resolution is to take both hunks, ordering them in reverse xmas tree style.
next prev parent reply other threads:[~2025-10-30 1:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 0:30 linux-next: manual merge of the ath-next tree with the ath tree Stephen Rothwell
2025-10-30 1:14 ` Jeff Johnson [this message]
2025-11-06 0:56 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-08-08 0:43 Stephen Rothwell
2024-08-08 5:13 ` Kalle Valo
2024-08-14 1:00 ` Stephen Rothwell
2024-08-15 14:04 ` Kalle Valo
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=83c8504d-3159-4a87-a1ea-0fef46bf6762@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=aditya.kumar.singh@oss.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maharaja.kennadyrajan@oss.qualcomm.com \
--cc=miaoqing.pan@oss.qualcomm.com \
--cc=sfr@canb.auug.org.au \
/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