From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Conor Dooley <conor@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm/arm64: samsung: Enable W=1 on dtbs by default
Date: Fri, 26 Jan 2024 11:31:15 +0100 [thread overview]
Message-ID: <6f5172d1-b741-4bae-8e30-c3a3d99197e7@linaro.org> (raw)
In-Reply-To: <20240125-unsaved-promoter-c0bc72bb4691@spud>
On 25/01/2024 18:51, Conor Dooley wrote:
>>>>
>>>> 64-bit has still few warnings:
>>>> https://krzk.eu/#/builders/29/builds/3710/steps/26/logs/warnings__6_
>>>
>>> I may move that graph check to W=2. There's some cases where port@1 is
>>> optional and it doesn't really make sense to fix these.
>>>
>>> Also, Conor wants to do this for all of riscv, but this solution is
>>> per directory. So I need to rework it to use a different variable that
>>> can be per directory or global.
>>
>> Just to clarify, because I still have this patch in my inbox: I assume
>> you are going to send a v2 of this, so I drop it.
>
> We got
> https://lore.kernel.org/linux-devicetree/20231122-dtc-warnings-v2-0-bd4087325392@kernel.org/
> out of this instead of a v2, did we not?
Indeed, I forgot.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-01-26 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 21:17 [PATCH] arm/arm64: samsung: Enable W=1 on dtbs by default Rob Herring
2023-11-17 10:19 ` Krzysztof Kozlowski
2023-11-21 14:58 ` Rob Herring
2024-01-25 11:31 ` Krzysztof Kozlowski
2024-01-25 17:51 ` Conor Dooley
2024-01-26 10:31 ` Krzysztof Kozlowski [this message]
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=6f5172d1-b741-4bae-8e30-c3a3d99197e7@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@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