Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752329AbbGVSKI (ORCPT ); Wed, 22 Jul 2015 14:10:08 -0400 Received: from mail-lb0-f171.google.com ([209.85.217.171]:33613 "EHLO mail-lb0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752242AbbGVSKF (ORCPT ); Wed, 22 Jul 2015 14:10:05 -0400 MIME-Version: 1.0 In-Reply-To: References: <1433272747-27114-1-git-send-email-ttnguyen@apm.com> <20150714084004.GA14593@localhost> Date: Wed, 22 Jul 2015 11:10:03 -0700 Message-ID: Subject: Re: [PATCH 0/2 RESEND] power: reset: Add syscon reboot/poweroff device nodes for APM X-Gene platform From: Loc Ho To: Olof Johansson Cc: Tai Nguyen , "arm@kernel.org" , Linux Kernel Mailing List , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "patches@apm.com" , Jon Masters Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2763 Lines: 65 Hi Olof,, >> >>>> This patch set adds syscon reboot/poweroff device nodes to support reboot and >>>> poweroff features on X-Gene platform. >>>> >>>> Tai Nguyen (2): >>>> power: reset: Add syscon reboot device node for APM X-Gene platform >>>> power: reset: Add syscon poweroff device node for APM X-Gene Mustang platform >>>> >>>> arch/arm64/boot/dts/apm/apm-mustang.dts | 12 ++++++++++++ >>>> arch/arm64/boot/dts/apm/apm-storm.dtsi | 12 ++++++++++++ >>>> 2 files changed, 24 insertions(+) >>> >>> Hi, >>> >>> It's unclear to me what you want to happen to these patches. They are >>> sent to a long list of to-recipients, one of which is arm@kernel.org. In >>> general, specify the person you want to take action on the patch in to >>> with the rest on cc. >> >> Is there an owner for all DT node files? Is that Catalina as he is >> owner for ARM64 arch folder? > > The ARM64 DT changes get merged through arm-soc, i.e. they get sent to > arm@kernel.org by the platform maintainers and picked up by us from > there (Arnd, Kevin or myself). > >>> We generally ask that patches first go to the subarch maintainers, >>> and they in turn send it on to us (either through a pull request or >>> by sending the patches to be applied). In the case of X-Gene, there is >>> no general platform maintainer so we keep getting patches from various >>> engineers at APM and it's unclear to us what your intentions are. >>> >>> I'd prefer to see one (to start with) person in charge of these (i.e. one >>> maintainer from the APM side). Please add that person to the MAINTAINERS >>> file as well. >> >> Are you suggesting that we have one person to start an GIT with >> kernel.org to keep all these misc ack'ed patches for X-Gene (APM) that >> don't seems to have an maintainer/home. Then request an pull by you? > > Pull requests are convenient for us, but if it's just a patch or two, > sending them directly in email is fine as well. If there is an chance in pulling this power off/reset patches for 4.2-rc4, can you pull in as patches? Otherwise, we will go the GIT pull request. > > What I want to avoid is a large number of people sending us patches > directly, which is why we ask for platform maintainers to coordinate > and aggregate patches to send on to us. That way we have one person > down the chain that we knows how we want the code delivered, and that > can do a round of reviews before we get it. We will get an GIT setup up for this and Duc Dang will contact you for pull request when ready. -Loc -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/