From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Zong Li <zong.li@sifive.com>,
Conor Dooley <conor.dooley@microchip.com>,
Bin Meng <bmeng.cn@gmail.com>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: dts: fu540-c000: fix duplicated dma compatible
Date: Tue, 26 Apr 2022 09:55:35 +0200 [thread overview]
Message-ID: <2ac59e59-2516-2bca-9db6-e2cfec671cef@linaro.org> (raw)
In-Reply-To: <f822fc7a-7c47-d8f9-8ef9-fda2c7832926@linaro.org>
On 26/04/2022 09:53, Krzysztof Kozlowski wrote:
> On 21/04/2022 08:54, Krzysztof Kozlowski wrote:
>> Remove duplicated compatible to fix error:
>>
>> u540-c000.dtsi:171.4-42: ERROR (duplicate_property_names): /soc/dma@3000000:compatible: Duplicate property name
>>
>> Fixes: 7eba954a8de8 ("riscv: dts: Add dma-channels property and modify compatible")
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> Hi everyone,
>
> This is an error which causes compilation to fail. Such patches should
> be picked up faster than later, because it breaks various builds.
>
> I'll take it via my tree.
Ah, it seems Palmer rebased his tree after it got accepted to next, so
patch can be dropped.
Best regards,
Krzysztof
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2022-04-26 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 6:54 [PATCH] riscv: dts: fu540-c000: fix duplicated dma compatible Krzysztof Kozlowski
2022-04-21 7:46 ` Bin Meng
2022-04-26 7:53 ` Krzysztof Kozlowski
2022-04-26 7:55 ` 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=2ac59e59-2516-2bca-9db6-e2cfec671cef@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=aou@eecs.berkeley.edu \
--cc=bmeng.cn@gmail.com \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=zong.li@sifive.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