From: "Arnd Bergmann" <arnd@arndb.de>
To: "Rahul T R" <r-ravikumar@ti.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
bjorn.andersson@linaro.org, "Shawn Guo" <shawnguo@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Marcel Ziswiler" <marcel.ziswiler@toradex.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
nm@ti.com
Cc: "Biju Das" <biju.das.jz@bp.renesas.com>,
"Vinod Koul" <vkoul@kernel.org>,
enric.balletbo@collabora.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Tomi Valkeinen" <tomi.valkeinen@ideasonboard.com>,
laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH] arm64: defconfig: Enable TI_TFP410 DVI bridge
Date: Thu, 03 Nov 2022 19:22:31 +0100 [thread overview]
Message-ID: <fd442f5d-68c4-4d4e-b913-d7c6b79bb0a4@app.fastmail.com> (raw)
In-Reply-To: <20221103180845.17076-1-r-ravikumar@ti.com>
On Thu, Nov 3, 2022, at 19:08, Rahul T R wrote:
> Enable TI_TFP410 DPI to DVI bridge. This is
> required to enable HDMI output on j721e-sk
> platform
>
> Signed-off-by: Rahul T R <r-ravikumar@ti.com>
The patch looks ok to me, but you have too many recipients
in Cc, so it's unclear who you expect to pick it up.
I expect Nishanth Menon will merge it into the k3 tree and
forward my it way along with the other 6.2 material.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2022-11-03 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221103180845.17076-1-r-ravikumar@ti.com>
2022-11-03 18:22 ` Arnd Bergmann [this message]
2022-11-03 21:46 ` [PATCH] arm64: defconfig: Enable TI_TFP410 DVI bridge Nishanth Menon
2022-11-04 2:54 ` Nishanth Menon
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=fd442f5d-68c4-4d4e-b913-d7c6b79bb0a4@app.fastmail.com \
--to=arnd@arndb.de \
--cc=biju.das.jz@bp.renesas.com \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=enric.balletbo@collabora.com \
--cc=geert+renesas@glider.be \
--cc=krzk@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=nm@ti.com \
--cc=r-ravikumar@ti.com \
--cc=shawnguo@kernel.org \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=vigneshr@ti.com \
--cc=vkoul@kernel.org \
--cc=will@kernel.org \
/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