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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 64167C4332F for ; Sun, 11 Dec 2022 13:34:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230075AbiLKNeZ (ORCPT ); Sun, 11 Dec 2022 08:34:25 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60826 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229845AbiLKNeV (ORCPT ); Sun, 11 Dec 2022 08:34:21 -0500 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 92E5826F0; Sun, 11 Dec 2022 05:34:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1670765658; x=1702301658; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=MwllUDJ4axGeJynb2FjYv02NOCKfwgtmyrW5PnmJ0S0=; b=Gl3YrCZvjnXsa/GqOEGgYoD67OckBXKnz/qvxt2xdF6CrfeaQjGDi0pM sStUoEnprdQkYDCGS7+aJ48I4kxBYrerJPOI+qCX0MYn2Wcg1FEojdlRp Gz7kklY57PepQN8yuA0AL4ID8NfT8t01F9f/T58nsfsKiz2SlV48WushY pQoBoKvK4aY2ux7TbpZlkLfFnueP2SqGjYgMgkk9i5qEgLkYBQnhjSlSD cCHYX6tiy9eNIoEZhLMbDN0SXVTA+EG8lJjQu3aBJ6A0ma58vPtdtW7Ht TIvhUgfe685RIWlY6T/aExCceO6fswSyYgH2fEx66bbq6K9f3MskYpLB5 g==; X-IronPort-AV: E=McAfee;i="6500,9779,10558"; a="382006497" X-IronPort-AV: E=Sophos;i="5.96,236,1665471600"; d="scan'208";a="382006497" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Dec 2022 05:34:17 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10558"; a="711390779" X-IronPort-AV: E=Sophos;i="5.96,236,1665471600"; d="scan'208";a="711390779" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga008.fm.intel.com with ESMTP; 11 Dec 2022 05:34:13 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1p4MT5-0080RS-0M; Sun, 11 Dec 2022 15:34:11 +0200 Date: Sun, 11 Dec 2022 15:34:10 +0200 From: Andy Shevchenko To: Jonathan Cameron Cc: Okan Sahin , outreachy@lists.linux.dev, Lee Jones , Rob Herring , Krzysztof Kozlowski , Liam Girdwood , Mark Brown , Lars-Peter Clausen , Caleb Connolly , Ramona Bolboaca , Geert Uytterhoeven , Lad Prabhakar , ChiYuan Huang , Anand Ashok Dumbre , William Breathitt Gray , Manish Narani , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-iio@vger.kernel.org Subject: Re: [PATCH 0/5] staging: drivers: mfd: Add MAX77541 MFD and related device drivers Message-ID: References: <20221207090906.5896-1-okan.sahin@analog.com> <20221211122043.424e095d@jic23-huawei> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221211122043.424e095d@jic23-huawei> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Dec 11, 2022 at 12:20:43PM +0000, Jonathan Cameron wrote: > On Wed, 7 Dec 2022 13:09:34 +0200 > Andy Shevchenko wrote: > > On Wed, Dec 07, 2022 at 12:08:39PM +0300, Okan Sahin wrote: > > > This patchset adds mfd, regulator and adc driver and related bindings.The patches > > > are required to be applied in sequence. > > > > You have an indentation / wrapping issues in the above text. > > > > Nevertheless, why staging? What does it mean? > > The main reason to go via staging is because a driver is sitting out > of tree and it is useful to bring it in on the basis that it can then be > cleaned up in tree before moving out of staging. But files are not in staging. Me being confused. > For a relatively small driver like this, that's hard to argue. Just > clean it up in response to review feedback and then we can take it > directly into relevant subsystems in the main tree. -- With Best Regards, Andy Shevchenko