public inbox for ath11k@lists.infradead.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: george.moussalem@outlook.com,
	Johannes Berg <johannes@sipsolutions.net>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
	ath11k@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/6] wifi: ath11k: add hw ring mask for QCN6122
Date: Wed, 29 Oct 2025 15:33:27 +0100	[thread overview]
Message-ID: <59ab13be-f72d-4567-a512-15b2c0be5ff4@kernel.org> (raw)
In-Reply-To: <20251029-ath11k-qcn6122-v1-3-58ed68eba333@outlook.com>

On 29/10/2025 15:26, George Moussalem via B4 Relay wrote:
> +};
> +
>  /* Target firmware's Copy Engine configuration for IPQ5018 */
>  const struct ce_pipe_config ath11k_target_ce_config_wlan_ipq5018[] = {
>  	/* CE0: host->target HTC control and raw streams */
> diff --git a/drivers/net/wireless/ath/ath11k/hw.h b/drivers/net/wireless/ath/ath11k/hw.h
> index 52d9f4c13b1366f2339b8900cf9db91e6ff1bcff..e7220c46de10c378ea5b452d78f921054ff54e54 100644
> --- a/drivers/net/wireless/ath/ath11k/hw.h
> +++ b/drivers/net/wireless/ath/ath11k/hw.h
> @@ -285,6 +285,7 @@ extern const struct ath11k_hw_ring_mask ath11k_hw_ring_mask_ipq8074;
>  extern const struct ath11k_hw_ring_mask ath11k_hw_ring_mask_qca6390;
>  extern const struct ath11k_hw_ring_mask ath11k_hw_ring_mask_qcn9074;
>  extern const struct ath11k_hw_ring_mask ath11k_hw_ring_mask_wcn6750;
> +extern const struct ath11k_hw_ring_mask ath11k_hw_ring_mask_qcn6122;

Why are you breaking the order in every such list? Keep it
alphabetically sorted.

Best regards,
Krzysztof


  reply	other threads:[~2025-10-29 14:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 14:26 [PATCH 0/6] wifi: ath11k: Add support for QCN6122 George Moussalem via B4 Relay
2025-10-29 14:26 ` [PATCH 1/6] dt: bindings: net: add bindings " George Moussalem via B4 Relay
2025-10-29 14:32   ` Krzysztof Kozlowski
2025-10-29 14:42     ` Krzysztof Kozlowski
2025-10-29 16:12     ` George Moussalem
2025-10-30  5:47       ` Krzysztof Kozlowski
2025-10-29 14:26 ` [PATCH 2/6] wifi: ath11k: add hw params " George Moussalem via B4 Relay
2025-10-29 14:26 ` [PATCH 3/6] wifi: ath11k: add hw ring mask " George Moussalem via B4 Relay
2025-10-29 14:33   ` Krzysztof Kozlowski [this message]
2025-10-29 14:26 ` [PATCH 4/6] wifi: ath11k: update hif and pci ops " George Moussalem via B4 Relay
2025-10-29 14:26 ` [PATCH 5/6] wifi: ath11k: add multipd support " George Moussalem via B4 Relay
2025-10-29 14:43   ` Krzysztof Kozlowski
2025-10-29 17:41     ` George Moussalem
2025-10-29 14:26 ` [PATCH 6/6] wifi: ath11k: add QCN6122 device support George Moussalem via B4 Relay

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=59ab13be-f72d-4567-a512-15b2c0be5ff4@kernel.org \
    --to=krzk@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=george.moussalem@outlook.com \
    --cc=jjohnson@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=robh@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