From: santosh.shilimkar@oracle.com
To: Jyri Sarha <jsarha@ti.com>,
dri-devel@lists.freedesktop.org, ssantosh@kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: tomi.valkeinen@ti.com, laurent.pinchart@ideasonboard.com,
peter.ujfalusi@ti.com, bparrot@ti.com, praneeth@ti.com,
robh+dt@kernel.org, mark.rutland@arm.com
Subject: Re: [PATCH resend 0/2] dts: keystone-k2g-evm: Display support
Date: Fri, 14 Feb 2020 09:40:55 -0800 [thread overview]
Message-ID: <6749076a-cbc1-d8e2-bc35-2e2a9ad80a6d@oracle.com> (raw)
In-Reply-To: <cover.1581671951.git.jsarha@ti.com>
On 2/14/20 1:22 AM, Jyri Sarha wrote:
> Resend because the earlier recipient list was wrong.
>
> Now that drm/tidss is queued for mainline, lets add display support for
> k2g-evm. There is no hurry since tidss is out only in v5.7, but it
> should not harm to have the dts changes in place before that.
>
> Jyri Sarha (2):
> ARM: dts: keystone-k2g: Add DSS node
> ARM: dts: keystone-k2g-evm: add HDMI video support
>
> arch/arm/boot/dts/keystone-k2g-evm.dts | 101 +++++++++++++++++++++++++
> arch/arm/boot/dts/keystone-k2g.dtsi | 22 ++++++
> 2 files changed, 123 insertions(+)
>
Ok. Will add this to the next queue.
Regards,
Santosh
next prev parent reply other threads:[~2020-02-14 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 9:22 [PATCH resend 0/2] dts: keystone-k2g-evm: Display support Jyri Sarha
2020-02-14 9:22 ` [PATCH resend 1/2] ARM: dts: keystone-k2g: Add DSS node Jyri Sarha
2020-02-14 9:22 ` [PATCH resend 2/2] ARM: dts: keystone-k2g-evm: add HDMI video support Jyri Sarha
2020-02-14 17:40 ` santosh.shilimkar [this message]
2020-06-02 8:13 ` [PATCH resend 0/2] dts: keystone-k2g-evm: Display support Tomi Valkeinen
2020-06-02 15:18 ` santosh.shilimkar
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=6749076a-cbc1-d8e2-bc35-2e2a9ad80a6d@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=peter.ujfalusi@ti.com \
--cc=praneeth@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=tomi.valkeinen@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).