From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: alsa-devel@alsa-project.org, kernel@stlinux.com,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Arnaud Pouliquen <arnaud.pouliquen@st.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] drm: sti: fix prototypes after API change
Date: Tue, 5 Jul 2016 09:38:10 +1000 [thread overview]
Message-ID: <20160705093810.1fe659f6@canb.auug.org.au> (raw)
In-Reply-To: <20160704131651.1083630-1-arnd@arndb.de>
Hi Arnd,
On Mon, 4 Jul 2016 15:16:51 +0200 Arnd Bergmann <arnd@arndb.de> wrote:
>
> Like the mediatek hdmi driver, the sti driver now suffers from
> an API change in linux-next:
>
> drivers/gpu/drm/sti/sti_hdmi.c:1250:15: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
> .hw_params = hdmi_audio_hw_params,
> ^~~~~~~~~~~~~~~~~~~~
> drivers/gpu/drm/sti/sti_hdmi.c:1250:15: note: (near initialization for 'audio_codec_ops.hw_params')
>
> This follows the API change, adding the extra function arguments.
> I suppose we want this to be part of the ASoC merge in linux-next
> for now too.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Fixes: 2c348e505328 ("drm: sti: Add ASoC generic hdmi codec support.")
> Fixes: efc9194bcff8 ("ASoC: hdmi-codec: callback function will be called with private data")
> Link: https://lkml.org/lkml/2016/6/29/441
Added to the sound-asoc merge from today.
--
Cheers,
Stephen Rothwell
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-07-04 23:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 13:16 [PATCH] drm: sti: fix prototypes after API change Arnd Bergmann
2016-07-04 13:22 ` Mark Brown
2016-07-04 13:27 ` Benjamin Gaignard
2016-07-04 13:36 ` Arnd Bergmann
2016-07-04 13:38 ` Mark Brown
2016-07-04 23:46 ` Stephen Rothwell
2016-07-04 23:59 ` Dave Airlie
2016-07-05 0:29 ` Stephen Rothwell
2016-07-04 23:38 ` Stephen Rothwell [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=20160705093810.1fe659f6@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@stlinux.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).