linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Joel Stanley <joel@jms.id.au>
Cc: Olof Johansson <olof@lixom.net>,
	linux-aspeed@lists.ozlabs.org,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Update ASPEED entry with details
Date: Wed, 11 Apr 2018 14:05:27 +0200	[thread overview]
Message-ID: <CAK8P3a0WbC+=FNBRv57i1B4jff66aLHVW6m0cJaj8_36K+Gp2w@mail.gmail.com> (raw)
In-Reply-To: <CACPK8XdX8d_=YVndzJLkt6rrA7S0NEBZ-ZZ2tg-nrrg=+CrMFA@mail.gmail.com>

On Wed, Apr 11, 2018 at 11:24 AM, Joel Stanley <joel@jms.id.au> wrote:
> On 11 April 2018 at 18:21, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Wed, Apr 11, 2018 at 6:06 AM, Joel Stanley <joel@jms.id.au> wrote:
>>
>> Sure, applied to the fixes branch now.
>>
>> In general, when you want a patch to be applied, please send it to
>> arm@kernel.org so we know it's for us. As a rule, I don't pick up patches
>> otherwise but assume that you are asking for feedback and/or Acks
>> but will resend it once everyone is happy with the change.
>
> Okay. Do we have these rules written down anywhere?
>
> If not, would you mind if I started a document on your behalf?

Please go ahead, we can definitely use something in Documentation/arm/
that explains our process, we don't really have anything written.

      Arnd

      reply	other threads:[~2018-04-11 12:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22  5:03 [PATCH] MAINTAINERS: Update ASPEED entry with details Joel Stanley
2018-02-22  8:39 ` Andrew Jeffery
2018-02-22  8:50   ` Wang, Haiyue
2018-02-23  0:11     ` Andrew Jeffery
2018-02-23  1:44       ` Wang, Haiyue
2018-04-11  4:06 ` Joel Stanley
2018-04-11  8:51   ` Arnd Bergmann
2018-04-11  9:24     ` Joel Stanley
2018-04-11 12:05       ` Arnd Bergmann [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='CAK8P3a0WbC+=FNBRv57i1B4jff66aLHVW6m0cJaj8_36K+Gp2w@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    /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).