Hello, On Wed, May 3, 2017 at 10:08 AM, Timur Tabi <[email protected]> wrote: > 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 >>> > [email protected], >>> > 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 [email protected] 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 > [email protected].
[email protected] 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 [email protected] for their platforms. So this should probably go in through Andy Gross? You didn't even cc him, so added now. > Anyway, I really hope it's not too late for my defconfig changes to make > 4.12. Please consider them. Thank you. 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. -Olof
