From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Alexandru Serdeliuc <serdeliuk@yahoo.com>,
Bjorn Andersson <andersson@kernel.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] dt-bindings: arm: qcom: Add Samsung Galaxy Z Fold5
Date: Thu, 28 Mar 2024 16:34:36 +0100 [thread overview]
Message-ID: <6b77633e-c501-4488-9b10-1881cfbf6f2c@linaro.org> (raw)
In-Reply-To: <20620ab0-5024-439e-943b-ab12d35a60d8@yahoo.com>
On 28.03.2024 4:10 PM, Alexandru Serdeliuc wrote:
> Hi Konrad,
>
> Thanks, I unfortunately sent the patch 2 prior seeing your reply.
>
> The warning was this one which says that i need to send the mods separately in two patches:
>
>>>>
>
>>>>WARNING: DT binding docs and includes should be a separate patch. See: Documentation/devicetree/bindings/submitting-patches.rst
Hm, if they were two separate patches, this is a false-positive. Could you
push the branch somewhere, so that we can report it to checkpatch maintainers?
>
>>>>
>
>
> I suppose that me sending two separate patches was not good, how i can fix this?
Please pick them both onto a single branch and send together as a series,
with a revision bump (v2) and mention that you made no changes other than
combining the two in the cover letter.
Konrad
next prev parent reply other threads:[~2024-03-28 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 14:31 [PATCH] dt-bindings: arm: qcom: Add Samsung Galaxy Z Fold5 Alexandru Marc Serdeliuc via B4 Relay
2024-03-28 14:39 ` Konrad Dybcio
2024-03-28 14:42 ` Alexandru Serdeliuc
2024-03-28 14:47 ` Konrad Dybcio
2024-03-28 15:10 ` Alexandru Serdeliuc
2024-03-28 15:34 ` Konrad Dybcio [this message]
2024-03-28 15:42 ` Alexandru Serdeliuc
2024-03-28 16:16 ` Krzysztof Kozlowski
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=6b77633e-c501-4488-9b10-1881cfbf6f2c@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).