From: Roger Quadros <rogerq@kernel.org>
To: Nishanth Menon <nm@ti.com>
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: Tue, 1 Feb 2022 21:00:03 +0200 [thread overview]
Message-ID: <58eab955-3c18-b56b-453e-e201df5e0f0c@kernel.org> (raw)
In-Reply-To: <20220201163341.u5etiz3zoi2t7h2x@briskly>
Hi Nishanth,
On 01/02/2022 18:33, Nishanth Menon wrote:
> On 07:28-20211223, Nishanth Menon wrote:
>> 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.
>
>
> Any updates?
>
I'll send out a re-based patch-set soon.
cheers,
-roger
prev parent reply other threads:[~2022-02-01 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 13:15 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
2022-02-01 16:33 ` Nishanth Menon
2022-02-01 19:00 ` Roger Quadros [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=58eab955-3c18-b56b-453e-e201df5e0f0c@kernel.org \
--to=rogerq@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--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
Powered by JetHome