From: Nathan Morrisson <nmorrisson@phytec.com>
To: "nm@ti.com" <nm@ti.com>
Cc: "upstream@lists.phytec.de" <upstream@lists.phytec.de>,
"afd@ti.com" <afd@ti.com>,
"kristo@kernel.org" <kristo@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"sashiko-reviews@lists.linux.dev"
<sashiko-reviews@lists.linux.dev>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [Upstream] [PATCH v4 1/2] dt-bindings: arm: ti: Add bindings for PHYTEC AM67x based hardware
Date: Thu, 3 Sep 2026 15:29:01 +0000 [thread overview]
Message-ID: <e7805ab3055241d5886f03407a71e87f3a6a42e4.camel@phytec.com> (raw)
In-Reply-To: <20260903132726.us2vplb7fey77mqw@clarity>
On Thu, 2026-09-03 at 08:27 -0500, Nishanth Menon wrote:
> On 18:20-20260902, Nathan Morrisson wrote:
> > Hello,
> > I just wanted to check on the status of these patches and see if
> > there
> > is any further action required by me.
>
> Could you rebase to 7.3-rc1 ? Sorry that this missed the window for
> what
> ever reason.
No problem, will do.
Regards,
Nathan
>
prev parent reply other threads:[~2026-09-03 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 17:31 [PATCH v4 1/2] dt-bindings: arm: ti: Add bindings for PHYTEC AM67x based hardware Nathan Morrisson
2026-06-30 17:31 ` [PATCH v4 2/2] arm64: dts: ti: Add support for the phyCORE-AM67x Nathan Morrisson
2026-09-02 18:20 ` [Upstream] [PATCH v4 1/2] dt-bindings: arm: ti: Add bindings for PHYTEC AM67x based hardware Nathan Morrisson
2026-09-03 13:27 ` Nishanth Menon
2026-09-03 15:29 ` Nathan Morrisson [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=e7805ab3055241d5886f03407a71e87f3a6a42e4.camel@phytec.com \
--to=nmorrisson@phytec.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=upstream@lists.phytec.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