From: Johannes Berg <johannes@sipsolutions.net>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
Ping-Ke Shih <pkshih@realtek.com>,
Sarika Sharma <quic_sarishar@quicinc.com>,
"ath12k@lists.infradead.org" <ath12k@lists.infradead.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] wifi: mac80211/ath12k: add support to fill link statistics of multi-link station
Date: Fri, 28 Feb 2025 01:47:02 +0100 [thread overview]
Message-ID: <98b73681e9ebe7e6252dc2a1d62cacf4b0524ff5.camel@sipsolutions.net> (raw)
In-Reply-To: <8bccb677-de56-475a-9b27-ccd55bcaebc5@oss.qualcomm.com>
On Thu, 2025-02-27 at 11:35 -0800, Jeff Johnson wrote:
> On 2/27/2025 1:32 AM, Johannes Berg wrote:
> > On Thu, 2025-02-27 at 09:30 +0000, Ping-Ke Shih wrote:
> > >
> > > I have encountered structural (not functional) dependency problem too.
> > > Could you share how I can tell NIPA the dependency between two patchset?
> > >
> >
> > I don't think you can at all, at this point.
>
> So it doesn't support the mechanism 'b4' can handle, namely having a
> base-commit: tag along with one or more prerequisite-patch-id: tags?
I don't really know, but I don't think so. Note that (afaict) b4 also
doesn't really use it to select the base to apply things to, it uses it
to make a 3-way merge to the tree you want to apply the patches to. I
doubt that would have helped here, given that it was trying to apply the
patches to the wireless-next tree, where that commit likely wouldn't
have been present anyway.
johannes
prev parent reply other threads:[~2025-02-28 0:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 4:58 [PATCH v3 0/5] wifi: mac80211/ath12k: add support to fill link statistics of multi-link station Sarika Sharma
2025-02-27 4:58 ` [PATCH v3 1/5] wifi: mac80211: correct RX stats packet increment for multi-link Sarika Sharma
2025-02-27 4:58 ` [PATCH v3 2/5] wifi: ath12k: add link support for multi-link in arsta Sarika Sharma
2025-02-27 4:58 ` [PATCH v3 3/5] wifi: ath12k: add EHT support for TX rate Sarika Sharma
2025-02-27 4:58 ` [PATCH v3 4/5] wifi: ath12k: correctly update bw for ofdma packets Sarika Sharma
2025-02-27 4:58 ` [PATCH v3 5/5] wifi: ath12k: fetch tx_retry and tx_failed from htt_ppdu_stats_user_cmpltn_common_tlv Sarika Sharma
2025-02-27 8:39 ` [PATCH v3 0/5] wifi: mac80211/ath12k: add support to fill link statistics of multi-link station Johannes Berg
[not found] ` <df26e3aeb3724d969f444eab65d8c872@realtek.com>
2025-02-27 9:32 ` Johannes Berg
2025-02-27 19:35 ` Jeff Johnson
2025-02-28 0:47 ` Johannes Berg [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=98b73681e9ebe7e6252dc2a1d62cacf4b0524ff5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath12k@lists.infradead.org \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=quic_sarishar@quicinc.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