From: Rob Herring <robh@kernel.org>
To: Anilkumar Kolli <akolli@codeaurora.org>
Cc: devicetree@vger.kernel.org, linux-wireless@vger.kernel.org,
ath11k@lists.infradead.org
Subject: Re: [PATCH v7 1/3] dt: bindings: net: update compatible for ath11k
Date: Tue, 8 Sep 2020 14:35:14 -0600 [thread overview]
Message-ID: <20200908203514.GA870402@bogus> (raw)
In-Reply-To: <010101746cb6751a-ca300933-1174-4534-a01b-b1dbf1c1f305-000000@us-west-2.amazonses.com>
On Tue, 08 Sep 2020 07:55:31 +0000, Anilkumar Kolli wrote:
> Add IPQ6018 wireless driver support,
> its based on ath11k driver.
>
> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org>
> ---
> V3:
> - Use 'enum' rather than oneOf+const.
> V4:
> - removed oneOf, use just enum (Rob)
> V5:
> - Fixes errors in 'make dt_binding_check' (Rob)
>
> Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.
If a tag was not added on purpose, please state why and what changed.
next prev parent reply other threads:[~2020-09-08 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1599551717-3801-1-git-send-email-akolli@codeaurora.org>
2020-09-08 7:55 ` [PATCH v7 1/3] dt: bindings: net: update compatible for ath11k Anilkumar Kolli
2020-09-08 20:35 ` Rob Herring [this message]
2020-09-10 15:48 ` Kalle Valo
2020-09-11 9:56 ` Kalle Valo
2020-09-08 7:55 ` [PATCH v7 2/3] ath11k: move target ce configs to hw_params Anilkumar Kolli
2020-09-08 7:55 ` [PATCH v7 3/3] ath11k: add ipq6018 support Anilkumar Kolli
[not found] ` <010101746cb68afd-6bca691b-12eb-40bd-bf2d-f22769b756ed-000000@us-west-2.amazonses.com>
2020-09-10 15:59 ` Kalle Valo
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=20200908203514.GA870402@bogus \
--to=robh@kernel.org \
--cc=akolli@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
--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