From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org
Subject: Re: drm/edid: sound/core: pcm_drm_eld.c compilation error in 4.2
Date: Thu, 16 Jul 2015 17:46:43 +0100 [thread overview]
Message-ID: <20150716164643.GM7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150716181658.553e6da7@armhf>
On Thu, Jul 16, 2015 at 06:16:58PM +0200, Jean-Francois Moine wrote:
> The file sound/core/pcm_drm_eld.c which was added by the commit
>
> 838d1631b766529213684f07dd71cdf2e92f0623
> ALSA: pcm: add DRM ELD helper
>
> lacks the function drm_eld_sad() which was defined by Russell's patch
>
> http://article.gmane.org/gmane.linux.ports.arm.kernel/411574
> drm/edid: add function to help find SADs
>
> This patch has not been applied.
Grr, that's the danger of trying to split changes which cross between
subsystems. I hate todays fragmented nature of kernel development,
it's really a nightmare.
I'm not sure how this can be resolved now, I asked Dave Airlie to pull
the next set of patches which include the one adding the SAD helper;
he's probably already pulled that for -next, so to pull out just that
patch and try to get it merged into -rc is going to be far from nice,
and will probably introduce conflicts.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-07-16 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 16:16 drm/edid: sound/core: pcm_drm_eld.c compilation error in 4.2 Jean-Francois Moine
2015-07-16 16:46 ` Russell King - ARM Linux [this message]
2015-07-17 10:45 ` Takashi Iwai
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=20150716164643.GM7557@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=moinejf@free.fr \
/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).