From: Heiko Stuebner <heiko@sntech.de>
To: Jagan Teki <jagannadh.teki@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Michael Trimarchi <michael@amarulasolutions.com>,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [PATCH] ARM: dts: rk3288-vyasa: Enable mali GPU node
Date: Tue, 26 Sep 2017 10:01:01 +0200 [thread overview]
Message-ID: <28439781.mnKO5aTto3@phil> (raw)
In-Reply-To: <1506365347-18655-1-git-send-email-jteki@openedev.com>
Am Dienstag, 26. September 2017, 00:19:07 CEST schrieb Jagan Teki:
> From: Jagan Teki <jagan@amarulasolutions.com>
>
> Enable mali GPU node for rk3288 vyasa board.
>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
applied for 4.15 after changing the subject to
"ARM: dts: rockchip: Enable mali GPU node on rk3288-vyasa"
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: rk3288-vyasa: Enable mali GPU node
Date: Tue, 26 Sep 2017 10:01:01 +0200 [thread overview]
Message-ID: <28439781.mnKO5aTto3@phil> (raw)
In-Reply-To: <1506365347-18655-1-git-send-email-jteki@openedev.com>
Am Dienstag, 26. September 2017, 00:19:07 CEST schrieb Jagan Teki:
> From: Jagan Teki <jagan@amarulasolutions.com>
>
> Enable mali GPU node for rk3288 vyasa board.
>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
applied for 4.15 after changing the subject to
"ARM: dts: rockchip: Enable mali GPU node on rk3288-vyasa"
Heiko
next prev parent reply other threads:[~2017-09-26 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 18:49 [PATCH] ARM: dts: rk3288-vyasa: Enable mali GPU node Jagan Teki
2017-09-25 18:49 ` Jagan Teki
2017-09-26 8:01 ` Heiko Stuebner [this message]
2017-09-26 8:01 ` Heiko Stuebner
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=28439781.mnKO5aTto3@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=jagan@amarulasolutions.com \
--cc=jagannadh.teki@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=michael@amarulasolutions.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.