All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: Tony Dinh <mibodhi@gmail.com>,
	U-Boot Mailing List <u-boot@lists.denx.de>
Cc: "Marek Beh�n" <marek.behun@nic.cz>,
	"Pali Roh�r" <pali@kernel.org>,
	"David Purdy" <david.c.purdy@gmail.com>,
	"Tom Rini" <trini@konsulko.com>
Subject: Re: [PATCH v2 8/8] arm: kirkwood: Pogoplug-V4 : Add board maintainer
Date: Thu, 13 Jan 2022 14:40:40 +0100	[thread overview]
Message-ID: <d59ff1e1-94d1-52a1-3190-4d763a7760bb@denx.de> (raw)
In-Reply-To: <20211223072649.13237-9-mibodhi@gmail.com>

On 12/23/21 08:26, Tony Dinh wrote:
> Add board maintainer for Pogoplug V4 board
> 
> Signed-off-by: Tony Dinh <mibodhi@gmail.com>

Hmm, just this one file?

I would prefer to not have this many patches in this series and squash
at least all files in the board directory into one. Or also integrate
the defconfig and include/configs header. This is my personal taste,
other might have different preferences here.

Thanks,
Stefan

> ---
> 
> (no changes since v1)
> 
>   board/cloudengines/pogo_v4/MAINTAINERS | 6 ++++++
>   1 file changed, 6 insertions(+)
>   create mode 100644 board/cloudengines/pogo_v4/MAINTAINERS
> 
> diff --git a/board/cloudengines/pogo_v4/MAINTAINERS b/board/cloudengines/pogo_v4/MAINTAINERS
> new file mode 100644
> index 0000000000..35fd7858b7
> --- /dev/null
> +++ b/board/cloudengines/pogo_v4/MAINTAINERS
> @@ -0,0 +1,6 @@
> +POGO_V4 BOARD
> +M:	Tony Dinh <mibodhi@gmail.com>
> +S:	Maintained
> +F:	board/cloudengines/pogo_v4/
> +F:	include/configs/pogo_v4.h
> +F:	configs/pogo_v4_defconfig
> 

Viele Grüße,
Stefan Roese

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-51 Fax: (+49)-8142-66989-80 Email: sr@denx.de

  reply	other threads:[~2022-01-13 13:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23  7:26 [PATCH v2 0/8] arm: kirkwood: Add support for Pogoplug V4 Tony Dinh
2021-12-23  7:26 ` [PATCH v2 1/8] arm: kirkwood: Pogoplug-V4 : Add DTS files Tony Dinh
2022-01-13 13:32   ` Stefan Roese
2021-12-23  7:26 ` [PATCH v2 2/8] arm: kirkwood: Pogoplug V4 : Add board defconfig file Tony Dinh
2022-01-13 13:33   ` Stefan Roese
2021-12-23  7:26 ` [PATCH v2 3/8] arm: kirkwood: Pogoplug-V4 : Add Kconfig files Tony Dinh
2022-01-13 13:35   ` Stefan Roese
2021-12-23  7:26 ` [PATCH v2 4/8] arm: kirkwood: Pogoplug-V4 : Add board include configs file Tony Dinh
2022-01-13 13:32   ` Stefan Roese
2022-01-13 13:36     ` Tom Rini
2022-01-14  0:50       ` Tony Dinh
2022-01-14  1:41         ` Tom Rini
2021-12-23  7:26 ` [PATCH v2 5/8] arm: kirkwood: Pogoplug-V4 : Add board kwbimage file Tony Dinh
2022-01-13 13:36   ` Stefan Roese
2021-12-23  7:26 ` [PATCH v2 6/8] arm: kirkwood: Pogoplug-V4 : Add board Make file Tony Dinh
2022-01-13 13:37   ` Stefan Roese
2021-12-23  7:26 ` [PATCH v2 7/8] arm: kirkwood: Pogoplug-V4 : Add board implementation Tony Dinh
2022-01-13 13:38   ` Stefan Roese
2021-12-23  7:26 ` [PATCH v2 8/8] arm: kirkwood: Pogoplug-V4 : Add board maintainer Tony Dinh
2022-01-13 13:40   ` Stefan Roese [this message]
2022-01-13 23:32     ` Tony Dinh

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=d59ff1e1-94d1-52a1-3190-4d763a7760bb@denx.de \
    --to=sr@denx.de \
    --cc=david.c.purdy@gmail.com \
    --cc=marek.behun@nic.cz \
    --cc=mibodhi@gmail.com \
    --cc=pali@kernel.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.