From: Maxime Ripard <maxime@cerno.tech>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
dri-devel@lists.freedesktop.org, Jaroslav Kysela <perex@perex.cz>,
Mark Brown <broonie@kernel.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [GIT PULL] HDMI codec improvements, v2
Date: Wed, 16 Jun 2021 09:23:31 +0200 [thread overview]
Message-ID: <20210616072331.l6z6sywlfyrg3x2z@gilmour> (raw)
In-Reply-To: <20210610122550.jnriewchqspdcrwk@gilmour>
Hi Thomas,
On Thu, Jun 10, 2021 at 02:25:50PM +0200, Maxime Ripard wrote:
> Hi,
>
> Here's a PR for the changes to hdmi-codec that need to be shared between
> drm-misc-next and ASoC.
>
> This is the second iteration, fixing a bisection issue with compilation
>
> Thanks!
> Maxime
>
>
> The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:
>
> Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git tags/asoc-hdmi-codec-improvements-v2
>
> for you to fetch changes up to 2fef64eec23a0840c97977b16dd8919afaffa876:
>
> ASoC: hdmi-codec: Add a prepare hook (2021-06-10 11:48:56 +0200)
>
> ----------------------------------------------------------------
> Improvements to the hdmi-codec driver and ALSA infrastructure around it
> to support the HDMI Channel Mapping and IEC958 controls
This has been merged into the ASoC tree [1], can you merge it in drm-misc-next?
Thanks!
Maxime
1: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=116b1e12b72f308b28af5b17081fdb9e1942a8ea
next prev parent reply other threads:[~2021-06-16 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 12:25 [GIT PULL] HDMI codec improvements, v2 Maxime Ripard
2021-06-16 7:23 ` Maxime Ripard [this message]
2021-06-23 12:13 ` Maxime Ripard
2021-06-23 13:14 ` o1bigtenor
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=20210616072331.l6z6sywlfyrg3x2z@gilmour \
--to=maxime@cerno.tech \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=tzimmermann@suse.de \
/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).