From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: arm64: Remove boot/dts/ directory from arm64 entry
Date: Wed, 11 Jul 2018 10:43:33 +0100 [thread overview]
Message-ID: <20180711094333.GC13963@arm.com> (raw)
In-Reply-To: <CAMuHMdUqRXde5DNgK6ih+ivuwY9HFbcWwbx_x3q5PmFcrGi0pQ@mail.gmail.com>
Hi Geert,
On Tue, Jul 10, 2018 at 09:25:58AM +0200, Geert Uytterhoeven wrote:
> On Fri, Jul 6, 2018 at 2:22 PM Will Deacon <will.deacon@arm.com> wrote:
> > The arm-soc tree does a good job handling .dts files, so exclude them
> > from the ARM64 entry in MAINTAINERS.
> >
> > Cc: Catalin Marinas <catalin.marinas@arm.com>
> > Signed-off-by: Will Deacon <will.deacon@arm.com>
>
> Thanks for your patch!
>
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -2264,6 +2264,7 @@ L: linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
> > T: git git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> > S: Maintained
> > F: arch/arm64/
> > +X: arch/arm64/boot/dts/
> > F: Documentation/arm64/
>
> Please note that this does not cause checkpatch to point to the arm-soc
> tree, but does drop the reference to linux-arm-kernel, which may not
> be intentional?
I think this is ok, since all of the individual sub-directories do pick
up the mailing list. Otherwise, somebody needs to claim responsibility
for the top-level directory, but realistically if you're adding a new
subdirectory there then you're going to be working with the right folks
anyway.
Will
prev parent reply other threads:[~2018-07-11 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 12:22 [PATCH] MAINTAINERS: arm64: Remove boot/dts/ directory from arm64 entry Will Deacon
2018-07-06 17:29 ` Olof Johansson
2018-07-09 11:56 ` Will Deacon
2018-07-10 7:25 ` Geert Uytterhoeven
2018-07-10 14:42 ` Olof Johansson
2018-07-10 14:51 ` Geert Uytterhoeven
2018-07-11 9:43 ` Will Deacon [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=20180711094333.GC13963@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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.