From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-mips@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add include/dt-bindings/mips to MIPS
Date: Tue, 5 Jul 2022 12:23:28 +0200 [thread overview]
Message-ID: <20220705102328.GF9951@alpha.franken.de> (raw)
In-Reply-To: <20220613121408.8786-1-lukas.bulwahn@gmail.com>
On Mon, Jun 13, 2022 at 02:14:08PM +0200, Lukas Bulwahn wrote:
> Maintainers of the directory Documentation/devicetree/bindings/mips
> are also the maintainers of the corresponding directory
> include/dt-bindings/mips.
>
> Add the file entry for include/dt-bindings/mips to the appropriate
> section in MAINTAINERS.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Thomas, please pick this MAINTAINERS addition to your section.
>
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 1b30f6b69477..6bf0c0ff935f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -13362,6 +13362,7 @@ F: Documentation/devicetree/bindings/mips/
> F: Documentation/mips/
> F: arch/mips/
> F: drivers/platform/mips/
> +F: include/dt-bindings/mips/
>
> MIPS BOSTON DEVELOPMENT BOARD
> M: Paul Burton <paulburton@kernel.org>
> --
> 2.17.1
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-07-05 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 12:14 [PATCH] MAINTAINERS: add include/dt-bindings/mips to MIPS Lukas Bulwahn
2022-07-05 10:23 ` Thomas Bogendoerfer [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=20220705102328.GF9951@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lukas.bulwahn@gmail.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;
as well as URLs for NNTP newsgroup(s).