public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: "Nicolas Escande" <nico.escande@gmail.com>
To: "Jeff Johnson" <jeff.johnson@oss.qualcomm.com>,
	<ath12k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wifi: ath12k: fbx: Add missing htt_metadata flag in ath12k_dp_tx()
Date: Wed, 19 Feb 2025 19:33:15 +0100	[thread overview]
Message-ID: <D7WMZ4TCZKPB.2GBOWXBN8WKF9@gmail.com> (raw)
In-Reply-To: <7e120d90-bbe6-47f5-bf72-c1ee681c97a0@oss.qualcomm.com>

On Wed Feb 19, 2025 at 6:58 PM CET, Jeff Johnson wrote:
>
> checkpatch complains:
> WARNING:UNKNOWN_COMMIT_ID: Unknown commit id '5e8a373c8699', maybe rebased or not pulled?
>
> And I don't see such a change in kernel.org
>
> Perhaps this is an out-of-tree change that should be referenced in a different
> way?
>
> /jeff

Indeed I didn't realize that was not mainline, but just in our internal tree.
My bad. Honestly surprised this has never been pushed upstream.

So the corresponding patch I was refering to is this one:
https://git.codelinaro.org/clo/qsdk/oss/system/feeds/wlan-open/-/blob/win.wlan_host_opensource.3.0.r24/patches/ath11k/207-ath11k-Add-support-for-dynamic-vlan.patch

How would you like to proceed ? I can respin it without this wrong reference if
need be. But if one of you guys has a better fix or something we can drop it too

Thanks


  reply	other threads:[~2025-02-19 18:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 11:33 [PATCH] wifi: ath12k: fbx: Add missing htt_metadata flag in ath12k_dp_tx() Nicolas Escande
2025-01-25 20:23 ` Nicolas Escande
2025-02-12  4:07 ` Vasanthakumar Thiagarajan
2025-02-12  4:09   ` Vasanthakumar Thiagarajan
2025-02-19 17:58 ` Jeff Johnson
2025-02-19 18:33   ` Nicolas Escande [this message]
2025-02-20 15:18     ` Jeff Johnson
2025-02-20 15:46     ` Jeff Johnson
2025-02-20 17:49       ` Nicolas Escande
2025-02-20 21:40 ` Jeff Johnson

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=D7WMZ4TCZKPB.2GBOWXBN8WKF9@gmail.com \
    --to=nico.escande@gmail.com \
    --cc=ath12k@lists.infradead.org \
    --cc=jeff.johnson@oss.qualcomm.com \
    --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