From: Nishanth Menon <nm@ti.com>
To: Roger Quadros <rogerq@kernel.org>
Cc: <kishon@ti.com>, <vigneshr@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] arm64: dts: ti: k3-am64-main: Add GPMC & ELM nodes
Date: Thu, 23 Dec 2021 07:28:22 -0600 [thread overview]
Message-ID: <20211223132822.nhujenxwmdwtjruw@viral> (raw)
In-Reply-To: <9250e5ed-6d4a-9eae-93d4-90e5906ae166@kernel.org>
On 19:11-20211222, Roger Quadros wrote:
> Hi Nishanth,
>
> On 08/12/2021 15:15, Roger Quadros wrote:
> > Hi Nishanth,
> >
> > This series adds GPMC and ELM controller device tree nodes to
> > AM64 SoC's dtsi file.
> >
> > Changelog:
> > v2
> > - Fix register sizes for GPMC node.
> > - Disable GPMC and ELM nodes in board files. They will be enabled in
> > NAND card device tree overlay.
>
> Gentle reminder to pick this for -next
> GPMC + NAND side patches are already in queue for -next. Thanks.
just responding to the main thread: lets hold this back for next window.
the bindings need to be in master rc1 prior to the dts getting picked up.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D)/Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-23 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 13:15 [PATCH v2 0/2] arm64: dts: ti: k3-am64-main: Add GPMC & ELM nodes Roger Quadros
2021-12-08 13:15 ` [PATCH v2 1/2] arm64: dts: ti: k3-am64-main: Add GPMC memory controller node Roger Quadros
2021-12-08 13:15 ` [PATCH v2 2/2] arm64: dts: ti: k3-am64-main: Add ELM (Error Location Module) node Roger Quadros
2021-12-22 17:11 ` [PATCH v2 0/2] arm64: dts: ti: k3-am64-main: Add GPMC & ELM nodes Roger Quadros
2021-12-23 13:28 ` Nishanth Menon [this message]
2022-02-01 16:33 ` Nishanth Menon
2022-02-01 19:00 ` Roger Quadros
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=20211223132822.nhujenxwmdwtjruw@viral \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rogerq@kernel.org \
--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