Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 9 Nov 2022 09:53:46 -0500
From:   =?utf-8?B?TsOtY29sYXMgRi4gUi4gQS4=?= Prado 
        <nfraprado@collabora.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc:     Arnd Bergmann <arnd@arndb.de>,
        Matthias Brugger <matthias.bgg@gmail.com>,
        kernel@collabora.com,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@collabora.com>,
        Bjorn Andersson <andersson@kernel.org>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
        Marcel Ziswiler <marcel.ziswiler@toradex.com>,
        Mark Brown <broonie@kernel.org>,
        Shawn Guo <shawnguo@kernel.org>, Vinod Koul <vkoul@kernel.org>,
        Will Deacon <will@kernel.org>,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/13] arm64: defconfig: Enable missing kconfigs for
 mt8183-kukui-jacuzzi-juniper
Message-ID: <20221109145346.prybmdztzc6imdbq@notapiano>
References: <20221108232228.1177199-1-nfraprado@collabora.com>
 <06c4f370-715d-4c66-ad43-143b652af5ff@app.fastmail.com>
 <d9690b4e-30a7-75be-5492-98206c3ccd99@linaro.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <d9690b4e-30a7-75be-5492-98206c3ccd99@linaro.org>
Precedence: bulk

On Wed, Nov 09, 2022 at 10:08:27AM +0100, Krzysztof Kozlowski wrote:
> On 09/11/2022 08:28, Arnd Bergmann wrote:
> > On Wed, Nov 9, 2022, at 00:22, N?colas F. R. A. Prado wrote:
> >> mt8183-kukui-jacuzzi-juniper is one of the devices set up to run tests
> >> on KernelCI, but several of its drivers are currently disabled in the
> >> defconfig. This series enables all the missing kconfigs on the defconfig
> >> to get everything probing on that machine so that it can be fully tested
> >> by KernelCI.
> > 
> > The changes all look fine, but I would recommend not separating it
> > out into 13 patches when you are doing just one thing here. 
> > 
> > As a general rule, if you keep saying the same things in each
> > patch description, it is usually an indication that they should
> > be combined. Similarly, if you find describing unrelated changes
> > ("also, ..."), that would be an indication that patches should
> > be split up.
> 
> I agree. Descriptions you wrote are useful - they explain why you are
> doing it - but it got all really too detailed, just for defconfigs. One
> commit per one symbol is a bit too much...

Okay, thank you both for the feedback. Given that this is a contentious file,
splitting independent symbols throughout the commits seemed to be more friendly
to possible merge conflicts. But you're right that there's a single overarching
goal for all the changes, so I'll join them all into a single commit as
suggested.

Thanks,
N?colas