mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Timur Tabi <timur@codeaurora.org>
To: Olof Johansson <olof@lixom.net>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	"arm@kernel.org" <arm@kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Will Deacon <will.deacon@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andy Gross <andy.gross@linaro.org>
Subject: Re: [PATCH] MAINTAINERS: add arm@kernel.org as the list for arm64 defconfig changes
Date: Wed, 3 May 2017 12:33:48 -0500	[thread overview]
Message-ID: <4b048ba1-b7e4-6ab6-95be-3163120f63aa@codeaurora.org> (raw)
In-Reply-To: <CAOesGMiY9o8199bb13gsd3SAs8YR-4rafYHoyV3VmK0dY0MDtQ@mail.gmail.com>

On 05/03/2017 12:26 PM, Olof Johansson wrote:
> arm@kernel.org as an email alias will break down if it starts being
> cc:d on large number of patches. Ideally we want the platform
> maintainers as filters/reviewers in front to keep the volume down. So
> far it's been kept to nearly only material from maintainers, and
> mostly pull requests.
> 
> Defconfig changes usually come in through maintainers. Said
> maintainers already know to send code to us at arm@kernel.org for
> their platforms. So this should probably go in through Andy Gross? You
> didn't even cc him, so added now.

How would I know to CC: him, or anyone else, without a MAINTAINERS entry?
I've already posted these patches 5 times, and every time I do, someone
tells me that I'm CCing the wrong person.

Are you saying that I should send the 9 patches to 9 different people, and
just pray that they all get merged in properly?  Each of the maintainers is
going to ask for an ACK from an ARM maintainer anyway, whoever he is (I
don't know any more).

There's got to be a better way.

> We won't consider any patches at this very time, since we're in the
> middle of the merge window. Main priority right now is to prepare the
> material we have for pull requests and merge.
> 
> This is not the time to send us new material, but you probably already
> know that.

Fair enough, but the patches aren't new.  They've been been floating on the
list for three weeks now.

-- 
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc.  Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.

  reply	other threads:[~2017-05-03 17:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 16:31 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 [this message]
2017-05-03 17:39         ` Olof Johansson
2017-05-03 17:47           ` Timur Tabi
2017-05-04 10:21             ` Will Deacon
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=4b048ba1-b7e4-6ab6-95be-3163120f63aa@codeaurora.org \
    --to=timur@codeaurora.org \
    --cc=andy.gross@linaro.org \
    --cc=arm@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=will.deacon@arm.com \
    /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

Powered by JetHome