From: Dhruva Gole <d-gole@ti.com>
To: <u-boot@lists.denx.de>
Subject: Re: [PATCH 1/3] arm: dts: k3-am62x: sync dt with linux kernel
Date: Thu, 3 Nov 2022 11:43:45 +0530 [thread overview]
Message-ID: <acce3647-e36a-94ee-c6fb-2dfca133ce4c@ti.com> (raw)
In-Reply-To: <20221103052101.l77rsp4siutbe72n@scientist>
Hi Nishanth,
On 03/11/22 10:51, Nishanth Menon wrote:
> On 20:23-20221027, Dhruva Gole wrote:
>> Sync the DT Files with linux kernel (tag v6.0.3)
> I dont see why we are'nt syncing all k3 dts files?
>
> That should be a separate series of it's own. And please use linus's tag
> like v6.0 instead of a stable tag.
Okay, will keep this in mind henceforth. However I do believe that the
DT sync in this particular case is the same as for the v6.0 tag as well.
>
> Please ensure to send verification logs over gist.github.com or
I have already included boot logs for k3-am625-sk evm in the cover
letter of this series:
https://lore.kernel.org/u-boot/20221027145311.523528-1-d-gole@ti.com/
> someplace similar to indicate success of boot of k3 platforms.
>
>
> [...]
--
Best regards,
Dhruva Gole
Texas Instruments Incorporated
next prev parent reply other threads:[~2022-11-03 6:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 14:53 [PATCH 0/3] AM62x SK EVM DT Sync + OSPI Support Dhruva Gole
2022-10-27 14:53 ` [PATCH 1/3] arm: dts: k3-am62x: sync dt with linux kernel Dhruva Gole
2022-11-03 5:21 ` Nishanth Menon
2022-11-03 6:13 ` Dhruva Gole [this message]
2022-11-04 12:22 ` Christian Gmeiner
2022-11-07 12:23 ` Gole, Dhruva
2022-12-09 22:53 ` Tom Rini
2022-10-27 14:53 ` [PATCH 2/3] arm: dts: Add OSPI support for AM62-SK Dhruva Gole
2022-12-09 22:53 ` Tom Rini
2022-10-27 14:53 ` [PATCH 3/3] configs: enable OSPI related configs in AM62x Dhruva Gole
2022-12-09 22:53 ` Tom Rini
2022-10-27 15:15 ` [PATCH 0/3] AM62x SK EVM DT Sync + OSPI Support Dhruva Gole
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=acce3647-e36a-94ee-c6fb-2dfca133ce4c@ti.com \
--to=d-gole@ti.com \
--cc=u-boot@lists.denx.de \
/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