linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: add maintainers for arm64 acpi
Date: Tue, 4 Mar 2014 11:15:21 +0000	[thread overview]
Message-ID: <20140304111520.GE8766@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CACxGe6tD3mQshDSoEQaPXAnXG_siUdiFoAWhjmO2gDY7ZzkjUw@mail.gmail.com>

On Tue, Mar 04, 2014 at 10:59:46AM +0000, Grant Likely wrote:
> On Tue, Mar 4, 2014 at 10:28 AM, Randy Dunlap <rdunlap@infradead.org> wrote:
> > On 03/03/2014 06:21 PM, Joe Perches wrote:
> >> On Tue, 2014-03-04 at 10:15 +0800, Graeme Gregory wrote:
> >>> Add maintainers for the arm-core file for arm64 ACPI support
> >>
> >> Shouldn't something have to be in the kernel
> >> tree before there's a MAINTAINERS entry?
> >
> > or in linux-next and the patch can be added to linux-next (some git tree).
> 
> Sure, it makes sense to merge this file along with the rest of the
> series, but I certainly appreciate that Graeme and Hanjun are willing
> to volunteer to do this work.

Well, to put it another way, it makes no sense at all to merge this patch
independently.

> On Tue, Mar 4, 2014 at 6:23 PM, Catalin Marinas <catalin.marinas@arm.com> wrote:
> > On Tue, Mar 04, 2014 at 02:15:45AM +0000, Graeme Gregory wrote:
> >> +ACPI ARM64
> >
> > That's a pretty broad statement for a single file. Is it core support,
> > architected peripherals, SoC?
> 
> That's a good point. Graeme, it would be good if you could put some
> text in the patch describing how you propose the maintainership to
> work. Unfortunately the maintainers file doesn't have any kind of
> comments field, otherwise I'd suggest you make those comments directly
> there.
> 
> Given that ACPI can touch a lot of subsystems I would expect you and
> Hanjun not to be merging much code directly, but being listed in
> maintainers means that you will be kept in the loop when it comes to
> merging ARM ACPI changes. I would also expect that anything that does
> go through you (instead of merely acked) would be merged via Rafael
> and Len's tree.
> 
> >
> >> +M:   Hanjun Guo <hanjun.guo@linaro.org>
> >> +M:   Graeme Gregory <graeme.gregory@linaro.org>
> >> +S:   Supported
> >> +L:   linux-acpi at vger.kernel.org
> >> +F:   drivers/acpi/plat/arm-core.c
> >
> > This patch should be part of the series introducing the arm-core.c file
> > and it will be ACKed (or NAKed) following review. We can't really commit
> > maintainers to a file which does not exist in mainline and while there is
> > still feedback to be addressed. It's like a blank cheque.
> 
> I agree with merging it with the rest of the series, but comparing it
> to a blank cheque is not appropriate. Merely having an entry in
> MAINTAINERS doesn't immediately confer trust or ability to merge code,
> but it does tell people who to talk to when looking at ACPI on ARM.
> You can bet that neither Linus, Len or Rafael will merge ARM ACPI
> trees from them if you disagree. (And even if they did, you would
> yell, and Linus would revert it).

If you want to know who to talk to regarding a subsystem then you use
get_maintainer.pl and/or git blame. Regardless of this patch, neither of
those tools will identify Graeme or Hanjun as the contacts for ACPI on ARM.

I think we're in agreement, but just to spell it out: this patch should be
included at the end of a series adding the files which will be maintained.

Will

  reply	other threads:[~2014-03-04 11:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  2:15 ARM64 ACPI Maintainers Graeme Gregory
     [not found] ` < 1393899345-7397-2-git-send-email-graeme.gregory@linaro.org>
2014-03-04  2:15 ` [PATCH] MAINTAINERS: add maintainers for arm64 acpi Graeme Gregory
2014-03-04  2:21   ` Joe Perches
2014-03-04  2:28     ` Randy Dunlap
2014-03-04 10:59       ` Grant Likely
2014-03-04 11:15         ` Will Deacon [this message]
2014-03-04 17:07           ` Grant Likely
2014-03-04 19:16         ` Graeme Gregory
2014-03-04 23:45         ` Catalin Marinas
2014-03-04 10:23   ` Catalin Marinas
2014-03-04 19:03     ` Graeme Gregory
2014-03-04 23:50       ` Catalin Marinas
2014-03-07 12:40         ` Grant Likely

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=20140304111520.GE8766@mudshark.cambridge.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 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).