Message-ID: <64934d64-3922-4cc1-a01d-6dcd773bc466@quicinc.com>
Date: Wed, 3 Jul 2024 17:39:41 +0800
From: Tengfei Fan <quic_tengfan@...cinc.com>
To: Krzysztof Kozlowski <krzk@...nel.org>, <andersson@...nel.org>,
        <konrad.dybcio@...aro.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
        <conor+dt@...nel.org>, <djakov@...nel.org>, <mturquette@...libre.com>,
        <sboyd@...nel.org>, <jassisinghbrar@...il.com>,
        <herbert@...dor.apana.org.au>, <davem@...emloft.net>,
        <manivannan.sadhasivam@...aro.org>, <will@...nel.org>,
        <joro@...tes.org>, <conor@...nel.org>, <tglx@...utronix.de>,
        <amitk@...nel.org>, <thara.gopinath@...il.com>,
        <linus.walleij@...aro.org>, <wim@...ux-watchdog.org>,
        <linux@...ck-us.net>, <rafael@...nel.org>, <viresh.kumar@...aro.org>,
        <vkoul@...nel.org>, <edumazet@...gle.com>, <kuba@...nel.org>,
        <pabeni@...hat.com>, <mcoquelin.stm32@...il.com>
CC: <robimarko@...il.com>, <bartosz.golaszewski@...aro.org>,
        <kishon@...nel.org>, <quic_wcheng@...cinc.com>,
        <alim.akhtar@...sung.com>, <avri.altman@....com>, <bvanassche@....org>,
        <agross@...nel.org>, <gregkh@...uxfoundation.org>,
        <quic_tdas@...cinc.com>, <robin.murphy@....com>,
        <daniel.lezcano@...aro.org>, <rui.zhang@...el.com>,
        <lukasz.luba@....com>, <quic_rjendra@...cinc.com>,
        <ulf.hansson@...aro.org>, <quic_sibis@...cinc.com>,
        <otto.pflueger@...cue.de>, <luca@...tu.xyz>,
        <neil.armstrong@...aro.org>, <abel.vesa@...aro.org>,
        <bhupesh.sharma@...aro.org>, <alexandre.torgue@...s.st.com>,
        <peppe.cavallaro@...com>, <joabreu@...opsys.com>,
        <netdev@...r.kernel.org>, <lpieralisi@...nel.org>, <kw@...ux.com>,
        <bhelgaas@...gle.com>, <ahalaney@...hat.com>,
        <krzysztof.kozlowski@...aro.org>, <u.kleine-koenig@...gutronix.de>,
        <dmitry.baryshkov@...aro.org>, <quic_cang@...cinc.com>,
        <danila@...xyga.com>, <quic_nitirawa@...cinc.com>,
        <mantas@...vices.com>, <athierry@...hat.com>,
        <quic_kbajaj@...cinc.com>, <quic_bjorande@...cinc.com>,
        <quic_msarkar@...cinc.com>, <quic_devipriy@...cinc.com>,
        <quic_tsoni@...cinc.com>, <quic_rgottimu@...cinc.com>,
        <quic_shashim@...cinc.com>, <quic_kaushalk@...cinc.com>,
        <quic_tingweiz@...cinc.com>, <quic_aiquny@...cinc.com>,
        <srinivas.kandagatla@...aro.org>, <linux-arm-msm@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-pm@...r.kernel.org>, <linux-clk@...r.kernel.org>,
        <linux-phy@...ts.infradead.org>, <linux-crypto@...r.kernel.org>,
        <linux-scsi@...r.kernel.org>, <linux-usb@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <iommu@...ts.linux.dev>,
        <linux-riscv@...ts.infradead.org>, <linux-gpio@...r.kernel.org>,
        <linux-watchdog@...r.kernel.org>, <linux-pci@...r.kernel.org>,
        <linux-stm32@...md-mailman.stormreply.com>, <kernel@...cinc.com>
Subject: Re: [PATCH 00/47] arm64: qcom: dts: add QCS9100 support



On 7/3/2024 12:45 PM, Krzysztof Kozlowski wrote:
> On 03/07/2024 05:56, Tengfei Fan wrote:
>> Introduce support for the QCS9100 SoC device tree (DTSI) and the
>> QCS9100 RIDE board DTS. The QCS9100 is a variant of the SA8775p.
>> While the QCS9100 platform is still in the early design stage, the
>> QCS9100 RIDE board is identical to the SA8775p RIDE board, except it
>> mounts the QCS9100 SoC instead of the SA8775p SoC.
> 
> The same huge patchset, to huge number of recipients was sent twice.
> First, sorry, this is way too big. Second, it has way too many
> recipients, but this is partially a result of first point. Only
> partially because you put here dozen of totally unrelated emails. Sorry,
> that does not make even sense. See form letter at the end how this
> works. Third, sending it to everyone twice is a way to annoy them off
> twice... Fourth,
> 
> Please split your work and do not cc dozen of unrelated folks.

I can split this patch series, there are two options for splitting:
Option A:
   1. Initial qcs9100.dtsi, qcs9100-pmics.dtsi, qcs9100-ride.dts renamed 
from sa8775p with existing compatible.

   2. Each subsystem have single patch series to each limited driver 
maintainers.

      - About 15 series need to update related drivers, so each series 
will have 3 patches (bindings, drivers, the compatible names in 
subsystem-related parts of dtsi/dts).

      - About 14 series only need to add qcs9100 compatible in 
bindings., so each series will have 2 patches (bindings, the compatible 
names in subsystem-related parts of dtsi/dts).

Option B:

   1. Each subsystem have single patch series to each limited driver 
maintainers. Each patch series only update bindings, drivers, but no 
compatible names change in dts.

      - About 15 series in total and each series will have 2 patches 
(bindings, drivers).

      - About 14 series only need to add qcs9100 compatible in bindings, 
so each series will have 1 patches (bindings).

   2. Squash current qcs9100.dtsi, qcs9100-pmics.dtsi, qcs9100-ride.dts 
with compatible changed to qcs9100 dt files.

We tend to use Option A.

Welcome to other ideas ideas for splitting the huge numbers of patches 
as well.

Another, each splited series will also have cover letter contain the 
whole story like this cover letter.

> 
> <form letter>
> Please use scripts/get_maintainers.pl to get a list of necessary people
> and lists to CC (and consider --no-git-fallback argument). It might
> happen, that command when run on an older kernel, gives you outdated
> entries. Therefore please be sure you base your patches on recent Linux
> kernel.
> 
> Tools like b4 or scripts/get_maintainer.pl provide you proper list of
> people, so fix your workflow. Tools might also fail if you work on some
> ancient tree (don't, instead use mainline), work on fork of kernel
> (don't, instead use mainline) or you ignore some maintainers (really
> don't). Just use b4 and everything should be fine, although remember
> about `b4 prep --auto-to-cc` if you added new patches to the patchset.
> </form letter>
> 
> Best regards,
> Krzysztof
> 

Previously, I've been using scripts/get_maintainers.pl to obtain a list 
of recipients and manually removing duplicate email addresses(although I 
noticed you have two different email addresses, so I included both).
I'll follow your advice and use b4 to submit a new version patch series 
to upstream, confident that similar issues won't arise again.

-- 
Thx and BRs,
Tengfei Fan

Powered by blists - more mailing lists