ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mihai Moldovan <ionic@ionic.de>
To: Jeff Johnson <quic_jjohnson@quicinc.com>, ath11k@lists.infradead.org
Subject: Re: [RFC] [PATCH 00/13] ath1{1,2}k: support multiple PCI devices in one system
Date: Fri, 22 Nov 2024 21:05:04 +0100	[thread overview]
Message-ID: <607a548e-7972-42e5-9c73-f928ebff81d9@ionic.de> (raw)
In-Reply-To: <872fd68a-b484-46b0-803d-9a6ceb823931@quicinc.com>


[-- Attachment #1.1: Type: text/plain, Size: 1240 bytes --]

* On 11/22/24 17:40, Jeff Johnson wrote:
>> When you post v2, please use scripts/get_maintainer.pl to identify all of the
>> maintainers and mailing lists that should be notified of this RFC.
>>
>> I suspect you won't get much feedback without doing so.
> 
> The sooner you post a v2 and include all of the right people and lists, the
> sooner the chances of getting good feedback. From internal WLAN team
> discussion the concept is good, but the implementation is not ideal. Hopefully
> pulling in the actual QRTR & MHI developers and maintainer will lead to a
> cleaner and acceptable solution.

Thank you, Jeff.

My initial idea was to not "spam" other lists with this RFC, because it depends 
on/is based on yet another RFC (c.f., Denis) which has been reviewed once, but 
has a few rough edges and isn't merge-ready yet. Since ath11k and ath12k are the 
only users of the new feature, I figured it would be more appropriate to post it 
here only.


Unfortunately, I have been swamped with work this week, so wasn't able to follow 
up on this.

I'll rebase against the newest tag, use get_maintainer.pl, checkpatch.pl, fix 
warnings and resubmit with a fixed cover letter some time this weekend.



Mihai

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

      reply	other threads:[~2024-11-22 20:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-17 16:05 [RFC] [PATCH 00/13] ath1{1,2}k: support multiple PCI devices in one system Mihai Moldovan
2024-11-17 16:06 ` [RFC] [PATCH 01/13] net: qrtr: support registering endpoint-specific data Mihai Moldovan
2024-11-17 16:06 ` [RFC] [PATCH 02/13] net: qrtr: mhi: register mhi_controller as " Mihai Moldovan
2024-11-17 16:06 ` [RFC] [PATCH 03/13] net: qrtr: smd: register rpmsg_device " Mihai Moldovan
2024-11-17 16:06 ` [RFC] [PATCH 04/13] net: qrtr: tun: register inode " Mihai Moldovan
2024-11-17 16:06 ` [RFC] [PATCH 05/13] soc: qcom: qmi_helpers: add QRTR endpoint ID to qmi_handle Mihai Moldovan
2024-11-17 16:06 ` [RFC] [PATCH 06/13] soc: qcom: qmi_helpers: optionally bind to QRTR endpoint ID in qmi_sock_create Mihai Moldovan
2024-11-17 16:06 ` [RFC] [PATCH 07/13] wifi: ath11k: add QRTR endpoint ID hif feature Mihai Moldovan
2024-11-17 16:06 ` [RFC] [PATCH 08/13] wifi: ath11k: stub QRTR endpoint ID fetching for AHB Mihai Moldovan
2024-11-17 16:06 ` [RFC] [PATCH 09/13] wifi: ath11k: implement QRTR endpoint ID fetching for PCI Mihai Moldovan
2024-11-17 16:06 ` [RFC] [PATCH 10/13] wifi: ath11k: bind to QRTR endpoint ID in ath11k_qmi_init_service Mihai Moldovan
2024-11-17 16:06 ` [RFC] [PATCH 11/13] wifi: ath12k: add QRTR endpoint ID hif feature Mihai Moldovan
2024-11-17 16:06 ` [RFC] [PATCH 12/13] wifi: ath12k: implement QRTR endpoint ID fetching for PCI Mihai Moldovan
2024-11-17 16:06 ` [RFC] [PATCH 13/13] wifi: ath12k: bind to QRTR endpoint ID in ath12k_qmi_init_service Mihai Moldovan
2024-11-17 16:59 ` [RFC] [PATCH 00/13] ath1{1,2}k: support multiple PCI devices in one system Mihai Moldovan
2024-11-18 15:52   ` Jeff Johnson
2024-11-22 16:40     ` Jeff Johnson
2024-11-22 20:05       ` Mihai Moldovan [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=607a548e-7972-42e5-9c73-f928ebff81d9@ionic.de \
    --to=ionic@ionic.de \
    --cc=ath11k@lists.infradead.org \
    --cc=quic_jjohnson@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