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 alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 37F47C433FE for ; Fri, 14 Oct 2022 15:12:45 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 1EAA96AFB; Fri, 14 Oct 2022 17:11:53 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 1EAA96AFB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1665760363; bh=N/njfTWM92urhDh1tc8kt06mInCQV3hTHb5sdf7xqk0=; h=Date:From:To:Subject:References:In-Reply-To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=U758+wP4gs/0Au4mZ8KlC+K+87KRqq2dEmx9geDZVR4A4hmhmSwDzuChGWVluhjPT gxsuTvhseJ6CHcXzyeE4VN/Vk+iKiViVrVyDa6ycXNGK/EazaHg1G0SfxnaWIKmbmj xWobbV6BHtpPvxt8GL/GO8YAL8AjoKi3A5NyoHk8= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id BF72FF801F5; Fri, 14 Oct 2022 17:11:52 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 8AE31F80224; Fri, 14 Oct 2022 17:11:51 +0200 (CEST) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id F235DF800F3 for ; Fri, 14 Oct 2022 17:11:45 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz F235DF800F3 Authentication-Results: alsa1.perex.cz; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="DDO5aBbZ" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1665760308; x=1697296308; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=N/njfTWM92urhDh1tc8kt06mInCQV3hTHb5sdf7xqk0=; b=DDO5aBbZgreLH6nkmVmu92TMI0Usnp2n7otpA35wzBHmJ2icFYrbFmB0 SMBceCrOJiZzM9BE2wLNWhh8CvQxoNElXnhUBhmKKWICY3nnumXU9juLi ChxT3chj6kMCY/dvfg5KxpexfxF3Cx7sBXO+rR7xJtHR+h5MzvxoFcUrz exm7P0GoxzA+BeEdg/qj58B1OwTytXWuX40CX9Q20+1U0Hiz0l41gbOzT iiqIrLi3+JE41eYyOWBY76qwVQR/Zjgp1oVFThMNEfivajFsAbM1XNaKn razdm3C1nKuVFnOIU0W+/nW6seFkVlGs/ie+Msmnyth/kVbTmnQm6OA47 A==; X-IronPort-AV: E=McAfee;i="6500,9779,10500"; a="331915101" X-IronPort-AV: E=Sophos;i="5.95,184,1661842800"; d="scan'208";a="331915101" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Oct 2022 08:11:42 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10500"; a="660758830" X-IronPort-AV: E=Sophos;i="5.95,184,1661842800"; d="scan'208";a="660758830" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga001.jf.intel.com with ESMTP; 14 Oct 2022 08:11:36 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1ojMLW-006yCQ-0e; Fri, 14 Oct 2022 18:11:34 +0300 Date: Fri, 14 Oct 2022 18:11:33 +0300 From: Andy Shevchenko To: Florian Fainelli , Linus Walleij Subject: Re: [rft, PATCH v2 00/36] pinctrl: Clean up and add missed headers Message-ID: References: <20221010201453.77401-1-andriy.shevchenko@linux.intel.com> <0684f480-2092-d520-2c8e-bd9a2dca47e3@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Cc: Kent Gibson , linux-omap@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-aspeed@lists.ozlabs.org, patches@opensource.cirrus.com, Bartosz Golaszewski , linux-actions@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org, linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-rpi-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, linux-tegra@vger.kernel.org, linux-riscv@lists.infradead.org, alsa-devel@alsa-project.org, openbmc@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org, linux-media@vger.kernel.org X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Wed, Oct 12, 2022 at 01:04:10PM +0300, Andy Shevchenko wrote: > On Tue, Oct 11, 2022 at 11:56 PM Florian Fainelli wrote: > > On 10/10/2022 1:14 PM, Andy Shevchenko wrote: > > > Currently the header inclusion inside the pinctrl headers seems more arbitrary > > > than logical. This series is basically out of two parts: > > > - add missed headers to the pin control drivers / users > > > - clean up the headers of pin control subsystem > > > > > > The idea is to have this series to be pulled after -rc1 by the GPIO and > > > pin control subsystems, so all new drivers will utilize cleaned up headers > > > of the pin control. > > > > > > Please, review and comment. > > > > Did you really need to split this on a per-driver basis as opposed to > > just a treewide drivers/pinctrl, drivers/media and drivers/gpiolib patch > > set? > > > > 36 patches seems needlessly high when 4 patches could have achieve the > > same outcome. > > I can combine them if maintainers ask for that, nevertheless for Intel > pin control and GPIO drivers, which I care more about, I would like to > leave as separate changes (easy to see in history what was done). I can now tell why I don't like to combine. While doing a revert (it's not related to GPIO nor to pin control), it appears that I reverted extra bits as merge conflict resolution. This is per se is not an issue, but when I tried to find and reapply that missed piece I can't, because the patch is combined and Git simply ignores to have `git cherry-pick _something in the past_` done. But again, up to maintainers. -- With Best Regards, Andy Shevchenko