From: Timur Tabi <timur@codeaurora.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
will.deacon@arm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add arm@kernel.org as the list for arm64 defconfig changes
Date: Wed, 3 May 2017 12:08:21 -0500 [thread overview]
Message-ID: <95597ce9-a46f-1491-ae65-518ed8b8c44c@codeaurora.org> (raw)
In-Reply-To: <20170503170110.GB23620@e104818-lin.cambridge.arm.com>
On 05/03/2017 12:01 PM, Catalin Marinas wrote:
> On Wed, May 03, 2017 at 11:31:25AM -0500, Timur Tabi wrote:
>> > Any changes to arch/arm64/configs/defconfig must be sent to arm@kernel.org,
>> > otherwise they will not get picked up. Add a MAINTAINERS entry to ensure
>> > the get_maintainers includes it.
> There are other patches that go through arm@kernel.org like
> arch/arm64/boot/dts/ but the arm-soc guys didn't want a MAINTAINERS
> entry (I don't remember the reasons).
I'm happy to add additional paths/files, but without a MAINTAINERS entry,
how would anyone know to CC: that address? I posted 3 versions of my
defconfig patchset before someone told me that I had to send it to
arm@kernel.org.
Anyway, I really hope it's not too late for my defconfig changes to make
4.12. Please consider them. Thank you.
--
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.
next prev parent reply other threads:[~2017-05-03 17:08 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 [this message]
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
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=95597ce9-a46f-1491-ae65-518ed8b8c44c@codeaurora.org \
--to=timur@codeaurora.org \
--cc=arm@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®