From: Vignesh Raghavendra <vigneshr@ti.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Olof Johansson <olof@lixom.net>, SoC <soc@kernel.org>,
Nishanth Menon <nm@ti.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tero Kristo <kristo@kernel.org>, arm-soc <arm@kernel.org>
Subject: Re: [GIT PULL v2 2/2] arm64: dts: TI K3 updates for v5.17
Date: Thu, 23 Dec 2021 16:21:33 +0530 [thread overview]
Message-ID: <60e9a3ef-f717-bd2a-b722-01942e184fd0@ti.com> (raw)
In-Reply-To: <CAK8P3a1s7Ekhvwvt0DtndxwkzMwCD-2Y7Va58T_8gDdL0vZNVg@mail.gmail.com>
On 23/12/21 3:20 pm, Arnd Bergmann wrote:
> On Thu, Dec 23, 2021 at 10:40 AM Vignesh Raghavendra <vigneshr@ti.com> wrote:
>>
>> Hi,
>>
>> Please pull the device tree changes for TI K3 platforms for v5.17.
>>
>> Please note:
>> This adds a dtbs_check warning due to missing YAML binding for pinctrl-single compatible.
>> There also a checkpatch error for complex macro usage in dt-bindings
>> header defining pinmux marco which is harmless.
>>
>> v2:
>> Moved aliases from k3-j721s2.dtsi file and trimmed the list
>> as per Arnd's suggestion
>
> Sorry, I should have been clearer about what I asked from you. I have already
> pulled the first version of this branch, and a lot of stuff on top of
> it, so I can't
> easily replace the contents with a new version.
>
Oops, I did not realize that v1 was pulled.
> Can you send just patches for the difference between the two versions so we
> can apply that on top?
>
Sure, will send delta patches in a follow up PR. Thanks!
Regards
Vignesh
_______________________________________________
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:[~2021-12-23 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 9:40 [GIT PULL v2 1/2] arm64: TI K3 SoC configs changes for v5.17 Vignesh Raghavendra
2021-12-23 9:40 ` [GIT PULL v2 2/2] arm64: dts: TI K3 updates " Vignesh Raghavendra
2021-12-23 9:50 ` Arnd Bergmann
2021-12-23 10:51 ` Vignesh Raghavendra [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=60e9a3ef-f717-bd2a-b722-01942e184fd0@ti.com \
--to=vigneshr@ti.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=olof@lixom.net \
--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