From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>,
Jisheng Zhang <Jisheng.Zhang@synaptics.com>
Cc: SoC Team <soc@kernel.org>, Rob Herring <robh@kernel.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
DTML <devicetree@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: synaptics: add DT for AS370-RDK
Date: Thu, 7 Apr 2022 22:39:09 +0200 [thread overview]
Message-ID: <8fa6212c-a914-dcc4-c852-32a3948db99f@linaro.org> (raw)
In-Reply-To: <CAK8P3a2vkZVt1bb7-iDGaSHp20U9d8QXu6AcrUMceJSS9Q_-4Q@mail.gmail.com>
On 20/08/2021 21:55, Arnd Bergmann wrote:
> On Fri, Aug 20, 2021 at 12:27 PM Jisheng Zhang
> <Jisheng.Zhang@synaptics.com> wrote:
>> On Fri, 20 Aug 2021 11:59:30 +0200 Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com> wrote:
>>> On 20/08/2021 11:31, Jisheng Zhang wrote:
>>>
>>> There is no such binding. You need to update the bindings file (first
>>> patch in the series).
>>
>> This is my plan ;) In fact, "berlin4ct" related binding is also missing.
>> I want to convert Documentation/devicetree/bindings/arm/syna.txt
>> to yaml, then add missing bindings. But it's too late for 5.15,
>>
>> If it's fine to keep as370.dtsi without board user(s), we can drop
>> this patch. I will solve this issue in next development window.
>
> Yes, doing it for the next cycle is ok.
Hi Arnd and Jisheng,
This patch was discussed in Aug 2021 and since then there was no resend.
I assume that AD370 will not get a board, so I propose to pick up my
removal patch:
https://lore.kernel.org/all/YRbDNInfG7caSr2r@robh.at.kernel.org/
I will resend it.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-04-07 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210820093108.UVR6RTUkPKFTAd8w4bVM5RVr2cKuyn7dsRVaSfNfdBc@z>
2021-08-20 9:31 ` [PATCH] arm64: dts: synaptics: add DT for AS370-RDK Jisheng Zhang
[not found] ` <20210820095930.XD0_2M84uagbk3eJ2KQwVAU6pAez3pBoIf6_IZi3VFo@z>
2021-08-20 9:59 ` Krzysztof Kozlowski
[not found] ` <20210820102708.vCv4lv-9jgWp3YYe8dZjIH-tw1Pfjft9FySDOFAmJuk@z>
2021-08-20 10:27 ` Jisheng Zhang
[not found] ` <20210820195553.qJ-Xpaoy9BfWOPaUbuYhFlLuKQEU4V5nLZ3kQDebPVs@z>
2021-08-20 19:55 ` Arnd Bergmann
2021-08-20 19:55 ` Arnd Bergmann
2022-04-07 20:39 ` 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=8fa6212c-a914-dcc4-c852-32a3948db99f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Jisheng.Zhang@synaptics.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=soc@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).