devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
	<devicetree@vger.kernel.org>, "Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH v3 01/12] dt: bindings: net: add bindings of WCN6750 for ath11k
Date: Mon, 28 Mar 2022 12:18:05 +0300	[thread overview]
Message-ID: <87sfr2zb8y.fsf@kernel.org> (raw)
In-Reply-To: <0256a6c6-088b-a7d5-68c4-b99238bbb0f4@quicinc.com> (Manikanta Pubbisetty's message of "Mon, 28 Mar 2022 11:43:47 +0530")

Manikanta Pubbisetty <quic_mpubbise@quicinc.com> writes:

> Sorry for top posting, missed to add device tree mail aliases.
> Adding them now.

IIRC DT maintainers use patchwork, so adding them to CC in a followup
email won't properly work.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2022-03-28  9:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220328060937.16738-1-quic_mpubbise@quicinc.com>
     [not found] ` <20220328060937.16738-2-quic_mpubbise@quicinc.com>
2022-03-28  6:13   ` [PATCH v3 01/12] dt: bindings: net: add bindings of WCN6750 for ath11k Manikanta Pubbisetty
2022-03-28  9:18     ` Kalle Valo [this message]
2022-03-28  9:19       ` Kalle Valo
2022-03-28  9:46         ` Manikanta Pubbisetty
2022-03-28  9:48 [PATCH v3 00/12] add support for WCN6750 Manikanta Pubbisetty
2022-03-28  9:48 ` [PATCH v3 01/12] dt: bindings: net: add bindings of WCN6750 for ath11k Manikanta Pubbisetty
2022-03-29 23:37   ` Rob Herring
2022-03-30  5:19     ` Manikanta Pubbisetty
2022-04-04 19:11   ` Matthias Kaehlcke
2022-04-05  6:25     ` Manikanta Pubbisetty

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=87sfr2zb8y.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_mpubbise@quicinc.com \
    --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;
as well as URLs for NNTP newsgroup(s).