From: Nishanth Menon <nm@ti.com>
To: Dhruva Gole <d-gole@ti.com>
Cc: Tom Rini <trini@konsulko.com>, Dave Gerlach <d-gerlach@ti.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
Suman Anna <s-anna@ti.com>, Gowtham Tammana <g-tammana@ti.com>,
Christian Gmeiner <christian.gmeiner@gmail.com>,
"Hari Nagalla" <hnagalla@ti.com>, Georgi Vlaev <g-vlaev@ti.com>,
Julien Panis <jpanis@baylibre.com>,
Aswath Govindraju <a-govindraju@ti.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH 1/3] arm: dts: k3-am62x: sync dt with linux kernel
Date: Thu, 3 Nov 2022 00:21:01 -0500 [thread overview]
Message-ID: <20221103052101.l77rsp4siutbe72n@scientist> (raw)
In-Reply-To: <20221027145311.523528-2-d-gole@ti.com>
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.
Please ensure to send verification logs over gist.github.com or
someplace similar to indicate success of boot of k3 platforms.
[...]
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2022-11-03 5:21 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 [this message]
2022-11-03 6:13 ` Dhruva Gole
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=20221103052101.l77rsp4siutbe72n@scientist \
--to=nm@ti.com \
--cc=a-govindraju@ti.com \
--cc=christian.gmeiner@gmail.com \
--cc=d-gerlach@ti.com \
--cc=d-gole@ti.com \
--cc=g-tammana@ti.com \
--cc=g-vlaev@ti.com \
--cc=hnagalla@ti.com \
--cc=jpanis@baylibre.com \
--cc=s-anna@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).