public inbox for linux-rockchip@lists.infradead.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Ezequiel Garcia <ezequiel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
Cc: Enric Balletbo i Serra
	<enric.balletbo-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>,
	linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	kernel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Manivannan Sadhasivam
	<manivannan.sadhasivam-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH] arm64: dts: rock960: Enable HDMI audio devices
Date: Sun, 03 Feb 2019 09:49:34 +0100	[thread overview]
Message-ID: <3467399.GglsX2lTEV@phil> (raw)
In-Reply-To: <e80f7cea65a51a2746aaef2c4efb1c1a474fbc1e.camel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>

Am Dienstag, 29. Januar 2019, 13:08:11 CET schrieb Ezequiel Garcia:
> On Tue, 2019-01-29 at 17:10 +0530, Manivannan Sadhasivam wrote:
> > On Tue, Jan 29, 2019 at 08:33:24AM -0300, Ezequiel Garcia wrote:
> > > This commit enable the hdmi-sound and i2s2 devices needed
> > > to have audio over HDMI.
> > > 
> > > Signed-off-by: Ezequiel Garcia <ezequiel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
> > 
> > Since this patch affects both Rock960 and Ficus, it should be mentioned
> > in the description. Other than that,

I've adapted the subject a bit (arm64: dts: rockchip: Eanble HDMI audio
devices on rk3399-rock960), mentioned rock960 and ficus in the message
and applied the result for 5.1

Thanks
Heiko

      parent reply	other threads:[~2019-02-03  8:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 11:33 [PATCH] arm64: dts: rock960: Enable HDMI audio devices Ezequiel Garcia
2019-01-29 11:40 ` Manivannan Sadhasivam
2019-01-29 12:08   ` Ezequiel Garcia
     [not found]     ` <e80f7cea65a51a2746aaef2c4efb1c1a474fbc1e.camel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2019-02-03  8:49       ` Heiko Stuebner [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=3467399.GglsX2lTEV@phil \
    --to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
    --cc=enric.balletbo-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
    --cc=ezequiel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
    --cc=kernel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=manivannan.sadhasivam-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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