linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Liviu Dudau <liviu@dudau.co.uk>
Cc: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Paul Burton" <paulburton@kernel.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: mips: Add bindings for TP-Link HC220 G5 v1 board
Date: Mon, 29 May 2023 22:00:20 +0100	[thread overview]
Message-ID: <20230529-unhook-alone-1b1bd6e6a226@spud> (raw)
In-Reply-To: <20230529150833.526084-3-liviu@dudau.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]

Hey,

On Mon, May 29, 2023 at 04:08:33PM +0100, Liviu Dudau wrote:
> Add bindings for the compatible string used for the TP-Link's
> HC220 G5 V1 board, a wireless AP based on MT7621.
> 
> Signed-off-by: Liviu Dudau <liviu@dudau.co.uk>

Two process things:
- Please run get_maintainer.pl against the current git tree - you seem
  to have missed 2 of the 3 dt-bindings maintainers. I don't mind my
  omission, but omitting Krzysztof means you're submitting patches based
  on a tree that is over a year old.
- Please don't send a v2 in reply to the v1.

> ---
>  Documentation/devicetree/bindings/mips/ralink.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/mips/ralink.yaml b/Documentation/devicetree/bindings/mips/ralink.yaml
> index 704b5b5951271..53c1f66353770 100644
> --- a/Documentation/devicetree/bindings/mips/ralink.yaml
> +++ b/Documentation/devicetree/bindings/mips/ralink.yaml
> @@ -80,6 +80,7 @@ properties:
>            - enum:
>                - gnubee,gb-pc1
>                - gnubee,gb-pc2
> +              - tplink,hc220-g5-v1

For the actual change though,
Acked-by: Conor Dooley <conor.dooley@microchip.com>

Thanks,
Conor.

>            - const: mediatek,mt7621-soc
>  
>  additionalProperties: true
> -- 
> 2.40.1
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-05-29 21:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 20:01 [PATCH] mips: dts: ralink: Add support for TP-Link HC220 G5 v1 board Liviu Dudau
2023-05-11 13:41 ` Arınç ÜNAL
2023-05-11 16:03   ` Liviu Dudau
2023-05-12  6:40     ` Arınç ÜNAL
2023-05-29 15:08       ` [PATCH v2 0/2] " Liviu Dudau
2023-05-29 15:08         ` [PATCH v2 1/2] " Liviu Dudau
2023-05-29 15:55           ` Liviu Dudau
2023-06-03 12:06             ` Arınç ÜNAL
2023-06-04 21:30               ` Liviu Dudau
2023-06-05  7:28                 ` Arınç ÜNAL
2023-06-03 12:10             ` Arınç ÜNAL
2023-05-29 15:08         ` [PATCH v2 2/2] dt-bindings: mips: Add bindings " Liviu Dudau
2023-05-29 21:00           ` Conor Dooley [this message]
2023-05-29 21:53             ` Liviu Dudau
2023-05-29 22:08               ` Conor Dooley
2023-05-30  3:35           ` Sergio Paracuellos
2023-05-11 13:43 ` [PATCH] mips: dts: ralink: Add support " Arınç ÜNAL
2023-05-11 13:59 ` Arınç ÜNAL

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=20230529-unhook-alone-1b1bd6e6a226@spud \
    --to=conor@kernel.org \
    --cc=arinc.unal@arinc9.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=liviu@dudau.co.uk \
    --cc=paulburton@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sergio.paracuellos@gmail.com \
    --cc=tsbogend@alpha.franken.de \
    /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).