From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_2 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1DB87C433DB for ; Wed, 27 Jan 2021 17:43:13 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id CAB8664DAC for ; Wed, 27 Jan 2021 17:43:12 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CAB8664DAC Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=9UsP//hMLts/ibKymsl+zY/s4fLtV5c3aXvsoEPCRYc=; b=zOLpCC0x5JBImhecLtBgKtkHg kj/GXGqO1sGawpzw25k75Xbk8+gF3RZJXFIfRx2Bs0/YeIXry9Yzyfp84MxqUg0p+RStJJcg5Qwzh 1Q48kdAMCQ2XwhCMP9kwmWxqcuvzbf7wSzjH0T69P/Vcm492MMzphE5x0UtxvWgk0S55Hfqot8ZYO fJtmQ9z7lI18sur4ouSzP5aSKPZNCNMucWKnE82m7RrhV2p1JQLlMEQrVE8omN6eH8uAUiRGQetPX vD3CNcaBPPFZE0e60l+B20F+gV5ztaRb8QQ9H1woLdSVYFt41si8ijZMbCBuQtEX6j9A3iPHQvDNt Vdd03M7qw==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1l4opM-0001Fs-1q; Wed, 27 Jan 2021 17:42:00 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1l4op5-00016A-Hb for linux-arm-kernel@lists.infradead.org; Wed, 27 Jan 2021 17:41:44 +0000 Received: by mail.kernel.org (Postfix) with ESMTPSA id 0DE9F64DA3; Wed, 27 Jan 2021 17:41:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1611769302; bh=ccTYH2EDWJwjCqgjMOwT8emAY3jhxENLNE9fZ1tIX50=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=p170fHNm+U8QcFUVjsMI4G/bsDyQmOyvglCZvtsmV0jIqq+lcVjv3T0czV4MXXJoX GyPiN0yLplbsvdHL8kra2a8irz4Y5J99EScXz9t74Kv/E4mCn1tiGCGWXIj7/oBnOF JHtys5oBgR+jnzTSpQUwuJFCKYKEKQlXJA4ja3IjFlIX2zJkveJ2+33OUw1c3F7srL jscXZ9H25mLxPMKhyipQCzL7yIXaX6DLOk7yGj99FH0ZC33/GGGl5IKOET4E5Acong zus0cZWM2QgD9UF0xJARD0JdxxPhGErNuttsQ0jXROgHHRqbikCBGjneUFt6DTQlc5 Zu6f98c92dGEA== Date: Wed, 27 Jan 2021 18:41:35 +0100 From: Mauro Carvalho Chehab To: Greg Kroah-Hartman Subject: Re: [PATCH v5 00/21] Move Hisilicon 6421v600 SPMI driver set out of staging Message-ID: <20210127184135.73dec9c3@coco.lan> In-Reply-To: References: <20210126175752.GF4839@sirena.org.uk> <20210126181124.GG4839@sirena.org.uk> <20210127100816.GH4903@dell> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210127_124143_793009_9EA2EE1F X-CRM114-Status: GOOD ( 38.61 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org, Mayulong , Stephen Boyd , linux-arm-msm@vger.kernel.org, Mark Brown , YueHaibing , Liam Girdwood , Wei Xu , linux-kernel@vger.kernel.org, Rob Herring , linux-arm-kernel@lists.infradead.org, Colin Ian King , Lee Jones , Dan Carpenter Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Em Wed, 27 Jan 2021 11:19:36 +0100 Greg Kroah-Hartman escreveu: > > This patch series finish addressing support for Hikey 970 > > SPMI controller, PMIC and regulators. > > > > This version was generated with -M, in order to make easier > > to merge upstream. Also, rebased on the top of v5.10, > > without any dependencies from the other patch series > > I'm submitting for this board. > > > > Yet, patch 18 to 20 modifies drivers/staging/hikey9xx/Kconfig > > and drivers/staging/hikey9xx/Makefile. So, trivial conflicts > > will rise if they're applied via different trees, as they all > > remove some lines from such files. > > I've applied the first 13 patches, except for patch 3, as that did not > apply, to my tree, thanks. Ok. I'll rebase the remaining patches on the top of staging-testing branch. > On Wed, Jan 27, 2021 at 10:08:16AM +0000, Lee Jones wrote: > > On Wed, 27 Jan 2021, Greg Kroah-Hartman wrote: > > > > > On Tue, Jan 26, 2021 at 06:11:24PM +0000, Mark Brown wrote: > > > > On Tue, Jan 26, 2021 at 07:02:39PM +0100, Greg Kroah-Hartman wrote: > > > > > On Tue, Jan 26, 2021 at 05:57:52PM +0000, Mark Brown wrote: > > > > > > > > > > Is there a branch we can pull from? > > > > > > > > > Once 0-day passes, you can pull from my staging-testing branch from > > > > > staging.git on git.kernel.org if you want. Give it 24 hours to pass > > > > > before it hits that location. > > > > > > > > Thanks. > > > > > > Should be out there now if you want to pull. > > > > > > > > Do you need a tag to pull from? > > > > > > > > It'd be nice but not essential. > > > > > > Why do you want/need this? Having these changes in your tree is good, > > > but what about other coding style cleanups that I will end up applying > > > over time before the 5.12-rc1 merge window opens? Are you wanting to > > > take the moved driver in your tree, or something else? > > > > > > Traditionally moving drivers out of staging can be done 2 ways: > > > - all happens in the staging tree, I take an ack from the > > > subsystem maintainer that this is ok to do. > > > - A new driver enters the "real" subsystem tree, and then I > > > delete the driver in the staging tree. This doesn't preserve > > > history as well (not at all), but can be easier for trees that > > > move quickly (like networking.) > > > > > > Which ever works for you is fine with me, but relying on the code to > > > stay "not touched" in my tree after you pull it almost never happens due > > > to the number of drive-by coding style cleanups that end up in the > > > staging tree every week. > > > > I would have expected the whole set to be merged as a set into a > > single tree, placed on an immutable branch and a pull-request to be > > sent out for the other maintainers to pull from (if they so wished). > > > > This would ensure development could continue on any/all of the > > affected drivers/files. > > > > If it's not too late, I'd be more than happy to facilitate. > > Given these patches are already in my public tree, that might be a bit > harder, why the huge work for this? Worst case, I just keep all of the > patches that do not actually move the code in my tree, and then things > can move after 5.12-rc1. Whatever works best for Lee/Mark. >From my side, I can re-submit the move patches and the DTS ones to be applied after 5.12-rc1, if this would be the preferred way. Thanks, Mauro _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel