MAINTAINERS: add [email protected] as the list for arm64 defconfig changes
PATCH 1/1 MAINTAINERS: add [email protected] as the list for arm64 defconfig changes
Any changes to arch/arm64/configs/defconfig must be sent to arm at kernel.org, otherwise they will not get picked up. Add a MAINTAINERS entry to ensure the get_maintainers includes it.
--- MAINTAINERS | 7 +++++++ 1 file changed, 7 insertions(+)
MAINTAINERS +7 -0
@@ -2066,6 +2066,13 @@ S: Maintained F: arch/arm64/ F: Documentation/arm64/ +ARM64 DEFCONFIG +M: Catalin Marinas <[email protected]> +M: Will Deacon <[email protected]> +L: arm at kernel.org +S: Maintained +F: arch/arm64/configs/defconfig + AS3645A LED FLASH CONTROLLER DRIVER M: Laurent Pinchart <[email protected]> L: linux-media at vger.kernel.org
Signature · 3 lines
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.
Quoted 3 lines · Timur Tabi
Any changes to
arch/arm64/configs/defconfigmust be sent to arm at kernel.org, otherwise they will not get picked up. Add aMAINTAINERSentry to ensure theget_maintainersincludes it.
arm at kernel.org is not a mailing list, it is an alias to those who deal with those requests.
Signature · 3 lines
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net.
Quoted 3 lines · Timur Tabi
Any changes to
arch/arm64/configs/defconfigmust be sent to arm at kernel.org, otherwise they will not get picked up. Add aMAINTAINERSentry to ensure theget_maintainersincludes it.
There are other patches that go through arm at kernel.org like arch/arm64/boot/dts/ but the arm-soc guys didn't want a MAINTAINERS entry (I don't remember the reasons).
Signature · 1 line
Catalin
Quoted 7 lines · Catalin Marinas
Quoted 3 lines · Timur Tabi
Quoted 3 lines
Any changes to
arch/arm64/configs/defconfigmust be sent to arm at kernel.org, otherwise they will not get picked up. Add aMAINTAINERSentry to ensure theget_maintainersincludes it.There are other patches that go through arm at kernel.org like
arch/arm64/boot/dts/but the arm-soc guys didn't want aMAINTAINERSentry (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 at kernel.org.
Anyway, I really hope it's not too late for my defconfig changes to make 4.12. Please consider them. Thank you.
Signature · 3 lines
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.
Quoted 5 lines · Timur Tabi
Quoted 4 lines · Catalin Marinas
Quoted 3 lines · Timur Tabi
Quoted 3 lines
Any changes to
arch/arm64/configs/defconfigmust be sent to arm at kernel.org, otherwise they will not get picked up. Add aMAINTAINERSentry to ensure theget_maintainersincludes it.
Quoted 8 lines
Quoted 3 lines
There are other patches that go through arm at kernel.org like
arch/arm64/boot/dts/but the arm-soc guys didn't want aMAINTAINERSentry (I don't remember the reasons).I'm happy to add additional paths/files, but without a
MAINTAINERSentry, 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 at kernel.org.
Most of the time it's the arm-soc guys pushing changes to defconfig, though on occasion the arm64 maintainers make some changes as well.
Quoted 2 lines
Anyway, I really hope it's not too late for my defconfig changes to make 4.12. Please consider them. Thank you.
I'm usually fine with such updates immediately after -rc1 but I can't speak for the arm-soc folk.
Signature · 1 line
Catalin
Hello,
Quoted 5 lines · Timur Tabi
Quoted 4 lines · Catalin Marinas
Quoted 3 lines · Timur Tabi
Quoted 3 lines
Any changes to
arch/arm64/configs/defconfigmust be sent to arm at kernel.org, otherwise they will not get picked up. Add aMAINTAINERSentry to ensure theget_maintainersincludes it.
Quoted 8 lines
Quoted 3 lines
There are other patches that go through arm at kernel.org like
arch/arm64/boot/dts/but the arm-soc guys didn't want aMAINTAINERSentry (I don't remember the reasons).I'm happy to add additional paths/files, but without a
MAINTAINERSentry, 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 at kernel.org.
arm at 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 at kernel.org for their platforms. So this should probably go in through Andy Gross? You didn't even cc him, so added now.
Quoted 2 lines
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
Quoted 10 lines · Olof Johansson
arm at 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 at 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.
Quoted 6 lines
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.
Signature · 3 lines
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.
Quoted 7 lines · Timur Tabi
Quoted 6 lines · Olof Johansson
arm at 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.
Quoted 8 lines
Quoted 4 lines
Defconfig changes usually come in through maintainers. Said maintainers already know to send code to us at arm at 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
MAINTAINERSentry? I've already posted these patches 5 times, and every time I do, someone tells me that I'm CCing the wrong person.
There's a handy tool called get_maintainer:
olof at brutus:~/work/linux ((52aa3ec...)) $ ./scripts/get_maintainer.pl -f arch/arm64/configs/defconfig
Catalin Marinas <[email protected]> (maintainer:ARM64 PORT (AARCH64 ARCHITECTURE),commit_signer:6/61=10%)
Will Deacon <[email protected]> (maintainer:ARM64 PORT (AARCH64 ARCHITECTURE)) Arnd Bergmann <[email protected]> (commit_signer:10/61=16%)
Kevin Hilman <[email protected]> (commit_signer:9/61=15%,authored:6/61=10%) Olof Johansson <[email protected]> (commit_signer:6/61=10%)
Wei Xu <[email protected]> (commit_signer:6/61=10%)
If you read the output, you can see that the people who have applied most of these patches have been Will, Arnd, Kevin and myself. Adding those on Cc could have been a good first step.
Quoted 6 lines
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.
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.
Quoted 9 lines
Quoted 6 lines
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.
While I understand your frustration, this is also not how it works at our end.
Sometimes we tweak defconfigs late in the merge window and sometimes even during early -rc, so let us get back to this after we've handled the merges.
-Olof
Quoted 3 lines · Olof Johansson
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.
Andy's being the platform maintainer is news to me. I'm not saying he isn't, but I can't remember the last time I involved him in any patches of ours.
Either way, I think there should be a designated maintainer for arch/arm64/configs/defconfig, and I think that person/alias should be in MAINTAINERS.
Quoted 3 lines
Sometimes we tweak defconfigs late in the merge window and sometimes even during early -rc, so let us get back to this after we've handled the merges.
Ok, thank you.
Signature · 3 lines
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.
Quoted 7 lines · Timur Tabi
Quoted 3 lines · Olof Johansson
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
Quoted 10 lines · Timur Tabi
Quoted 3 lines · Olof Johansson
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.
Andy's being the platform maintainer is news to me. I'm not saying he isn't, but I can't remember the last time I involved him in any patches of ours.
If it is Qualcomm related, it generally goes through me. And I send it up through the arm soc guys (kevin, olof, and arnd).
Quoted 4 lines
Either way, I think there should be a designated maintainer for
arch/arm64/configs/defconfig, and I think that person/alias should be inMAINTAINERS.
I disagree here. We've generally had defconfigs go up through the disparate ARM board maintainers and they get collated by arm-soc. It's easy when it's something like qcom_defconfig, but get_maintainer doesn't give you the correct name if you are going for multiv7 or some of the default configs.
Andy