From: Alexandru Serdeliuc <serdeliuk@yahoo.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
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:10:25 +0100 [thread overview]
Message-ID: <20620ab0-5024-439e-943b-ab12d35a60d8@yahoo.com> (raw)
In-Reply-To: <8e09b779-a18f-46b4-926c-40e2a5782d85@linaro.org>
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
>>>
I suppose that me sending two separate patches was not good, how i can
fix this?
Best regards,
Marc
On 28/3/24 15:47, Konrad Dybcio wrote:
> On 28.03.2024 3:42 PM, Alexandru Serdeliuc wrote:
>> Hi Konrad,
>>
>>
>> Thanks, yes, I am new to b4 and sending patches, in a few minutes I will add the second patch.
>>
>> That actually add the device tree, but without the previous patch it showed me a warning, and with both patches provided another warning that i need to split them in two.
> Oh no, you should send them together! Could you please paste the warning so that
> we can work out the issue?
>
> Konrad
next prev parent reply other threads:[~2024-03-28 16:11 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 [this message]
2024-03-28 15:34 ` Konrad Dybcio
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=20620ab0-5024-439e-943b-ab12d35a60d8@yahoo.com \
--to=serdeliuk@yahoo.com \
--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 \
/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).