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 arm@kernel.org as the list for arm64 defconfig changes
Date: Thu, 4 May 2017 11:21:15 +0100	[thread overview]
Message-ID: <20170504102114.GC5417@arm.com> (raw)
In-Reply-To: <0ad7d305-d323-339f-9534-d559f1cf656a@codeaurora.org>

On Wed, May 03, 2017 at 12:47:16PM -0500, Timur Tabi wrote:
> On 05/03/2017 12:39 PM, Olof Johansson wrote:
> > No, I'm not saying that, and there is a better way: Send it through
> > Andy if in doubt -- it should be his job as your platform maintainer
> > to help guide you through the system if needed.
> 
> Will told me that defconfig patches should go to arm at kernel.org, but you're
> telling me they should go to Andy instead.

defconfig patches go via arm at kernel.org, because they pick them up from the
platform maintainers. However, given that the merge window is open (and my
understanding is that you want these in for 4.12!), I suggested mailing them
directly to arm at kernel.org to get their opinion, which they promptly provided ;)

Apologies for the confusion,

Will

  reply	other threads:[~2017-05-04 10:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 16:31 [PATCH] MAINTAINERS: add arm@kernel.org as the list for arm64 defconfig changes Timur Tabi
2017-05-03 16:34 ` Russell King - ARM Linux
2017-05-03 17:01 ` Catalin Marinas
2017-05-03 17:08   ` Timur Tabi
2017-05-03 17:14     ` Catalin Marinas
2017-05-03 17:26     ` Olof Johansson
2017-05-03 17:33       ` Timur Tabi
2017-05-03 17:39         ` Olof Johansson
2017-05-03 17:47           ` Timur Tabi
2017-05-04 10:21             ` Will Deacon [this message]
2017-05-04 15:41             ` Andy Gross

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=20170504102114.GC5417@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).