linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: arm-soc maintainer entry
Date: Thu, 04 Oct 2012 11:49:21 -0700	[thread overview]
Message-ID: <506DDA31.9010503@codeaurora.org> (raw)
In-Reply-To: <CAOesGMjotnx_6HiwngRO9OaZYGGAexiwZ_shkOK7qROZcjDmqA@mail.gmail.com>

On 10/04/12 09:55, Olof Johansson wrote:
> Hi,
>
> On Thu, Oct 4, 2012 at 1:41 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>> Is the arm at kernel.org alias going to be added into the MAINTAINERS file?
>> Should anybody be sending mails to this address?
>>
>> It seems I asked this over a year ago and the response was positive but
>> nothing ever happened[1]. Maybe something like below? I only ask because
>> get_maintainer.pl isn't picking up this email.
> I've been holding off re-proposing this, mostly because life is easier
> for us if we don't get arm at kernel.org cc:d on every single patch by
> people who run get_maintainers.pl -- it's the equivalent of getting
> linux-arm-kernel cc:d to your inbox. It's better signal-to-noise ratio
> if it's mostly platform maintainers that email us on that address with
> pull requests or patches they want applied.
>
> But yeah, it also means that the maintainer structure is undocumented.
> I'm open for suggestions.
>

Thanks for clarifying. Maybe we can put in the git tree and no email
address? That at least documents some structure.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2012-10-04 18:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04  8:41 arm-soc maintainer entry Stephen Boyd
2012-10-04 16:55 ` Olof Johansson
2012-10-04 18:49   ` Stephen Boyd [this message]
2012-10-04 19:28     ` Olof Johansson

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=506DDA31.9010503@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --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).