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,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS 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 D1F69C433E0 for ; Wed, 27 Jan 2021 10:23:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7FDA420723 for ; Wed, 27 Jan 2021 10:23:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231142AbhA0KXH (ORCPT ); Wed, 27 Jan 2021 05:23:07 -0500 Received: from mail.kernel.org ([198.145.29.99]:49904 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235793AbhA0KUU (ORCPT ); Wed, 27 Jan 2021 05:20:20 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id D7AF320723; Wed, 27 Jan 2021 10:19:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1611742779; bh=d2h1EgBQMOjE5+8onjr7Xk6n8e+j+afxZeaitVsthDs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=d3XzXb/8FnxZ1Z+z/5HUsE1VWiFD1iFv7la249QYlq0mttvihgZY54uYl71wX/v3J rZnaGR6hUIp5u8D7f9DT9gQ1py/w3RRjWVJ96amv9pSOuUeGKhWT2FHh4iLA7tSVxv VYBz7WHULvVOjJ0hVgvY+RJayodaHXT6vS0A7tgE= Date: Wed, 27 Jan 2021 11:19:36 +0100 From: Greg Kroah-Hartman To: Lee Jones Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org, Rob Herring , Mayulong , Mauro Carvalho Chehab , linux-arm-msm@vger.kernel.org, YueHaibing , Liam Girdwood , Wei Xu , linux-kernel@vger.kernel.org, Stephen Boyd , Mark Brown , Dan Carpenter , Colin Ian King , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v5 00/21] Move Hisilicon 6421v600 SPMI driver set out of staging Message-ID: References: <20210126175752.GF4839@sirena.org.uk> <20210126181124.GG4839@sirena.org.uk> <20210127100816.GH4903@dell> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210127100816.GH4903@dell> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. thanks, greg k-h