Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Alexandru Serdeliuc <serdeliuk@yahoo.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] Samsung Galaxy Z Fold5 initial support
Date: Thu, 11 Apr 2024 09:34:55 +0200	[thread overview]
Message-ID: <37c5710a-426f-4054-8632-e24b9d920bcc@linaro.org> (raw)
In-Reply-To: <46bee5df-3d66-44c1-9d7a-86e32a2149dc@yahoo.com>

On 11/04/2024 08:36, Alexandru Serdeliuc wrote:
> Hi,
> 
> The list of changes  (changelog) from the cover is not what I should  add?
> 
> My patches received only two ACK tags, on V3 and on the initial request 
> (v1), I was not able to identify any other, I added them to their place 
> in the change log
> 
> ...
> - v3
>    . added b4 version 3
>    . removed address and size cells in device description
>    Acked-by: Rob Herring<robh@kernel.org>
> ...
> - v1
>    . The initial request was split in two patches sent due to the following checkpatch warning, was requested to re send them together:
>      WARNING: DT binding docs and includes should be a separate patch. See: Documentation/devicetree/bindings/submitting-patches.rst
>    Acked-by: Krzysztof Kozlowski<krzysztof.kozlowski@linaro.org>
> 
> I suppose that adding them to their place in change log is wrong, I 
> should create a v6 and put them at the end of the cover letter? Or how 
> to proceed?

Please don't top post. If you add them to the changelog, how are they
going to be effective? Please apply your patch (e.g. b4 shazam) and look
for them...

Submitting patches explains where to add tags. Look at other mailings.
And finally: why even bothering about this if b4 does it for you?

https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577

Best regards,
Krzysztof


  reply	other threads:[~2024-04-11  7:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 21:28 [PATCH v5 0/2] Samsung Galaxy Z Fold5 initial support Alexandru Marc Serdeliuc via B4 Relay
2024-04-10 21:28 ` [PATCH v5 1/2] dt-bindings: arm: qcom: Document the Samsung Galaxy Z Fold5 Alexandru Marc Serdeliuc via B4 Relay
2024-04-10 21:28 ` [PATCH v5 2/2] arm64: dts: qcom: sm8550: Add support for " Alexandru Marc Serdeliuc via B4 Relay
2024-04-11  6:03 ` [PATCH v5 0/2] Samsung Galaxy Z Fold5 initial support Krzysztof Kozlowski
2024-04-11  6:36   ` Alexandru Serdeliuc
2024-04-11  7:34     ` Krzysztof Kozlowski [this message]
2024-04-11  8:47       ` Krzysztof Kozlowski
2024-04-11  9:12         ` Alexandru Serdeliuc
2024-04-11 13:42 ` Rob Herring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=37c5710a-426f-4054-8632-e24b9d920bcc@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=serdeliuk@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox