From: Inki Dae <inki.dae@samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dave Airlie <airlied@linux.ie>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Hyungwon Hwang <human.hwang@samsung.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: linux-next: build failure after merge of the drm-exynos tree
Date: Wed, 24 Jun 2015 10:21:20 +0900 [thread overview]
Message-ID: <558A0610.7070405@samsung.com> (raw)
In-Reply-To: <20150624110122.2dcbc338@canb.auug.org.au>
Hi Dave and Stephen,
On 2015년 06월 24일 10:01, Stephen Rothwell wrote:
> Hi Dave,
>
> On Tue, 23 Jun 2015 11:52:45 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> After merging the drm-exynos tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> drivers/media/i2c/adv7604.o: In function `of_graph_get_endpoint_by_regs':
>> adv7604.c:(.text+0x586c): multiple definition of `of_graph_get_endpoint_by_regs'
>> drivers/media/i2c/adv7343.o:adv7343.c:(.text+0xa13): first defined here
>> drivers/media/platform/soc_camera/atmel-isi.o: In function `of_graph_get_endpoint_by_regs':
>> atmel-isi.c:(.text+0x1ec9): multiple definition of `of_graph_get_endpoint_by_regs'
>> drivers/media/platform/soc_camera/soc_camera.o:soc_camera.c:(.text+0x2ce3): first defined here
>> drivers/media/platform/soc_camera/rcar_vin.o: In function `of_graph_get_endpoint_by_regs':
>> rcar_vin.c:(.text+0x307c): multiple definition of `of_graph_get_endpoint_by_regs'
>> drivers/media/platform/soc_camera/soc_camera.o:soc_camera.c:(.text+0x2ce3): first defined here
>>
>> Caused by commit:
>>
>> a0f7001c18ca ("of: add helper for getting endpoint node of specific identifiers")
>
> This failure is now in the drm tree (where above patch is commit
> 8ccd0d0ca041). I have used the patch from Inki for today.
As you know, I posted below patch which fixes the build error,
[PATCH] of: fix a build error to f_graph_get_endpoint_by_regs function
However, I think we need Acked-by from device tree maintainer to merge
it to drm-next.
Thanks,
Inki Dae
>
next prev parent reply other threads:[~2015-06-24 1:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 1:52 linux-next: build failure after merge of the drm-exynos tree Stephen Rothwell
2015-06-23 5:30 ` Inki Dae
2015-06-23 5:30 ` Inki Dae
2015-06-24 1:01 ` Stephen Rothwell
2015-06-24 1:21 ` Inki Dae [this message]
2015-06-24 1:25 ` Dave Airlie
2015-06-24 1:25 ` Inki Dae
-- strict thread matches above, loose matches on Subject: below --
2015-08-17 3:51 Stephen Rothwell
2015-08-17 3:53 ` Stephen Rothwell
2015-08-17 5:53 ` Stephen Rothwell
2015-08-17 7:08 ` Inki Dae
2015-08-18 3:02 ` Stephen Rothwell
2025-08-21 1:27 Stephen Rothwell
2025-08-26 2:13 ` Stephen Rothwell
2025-09-01 2:22 ` Stephen Rothwell
2025-09-02 3:03 ` Stephen Rothwell
2025-09-03 15:51 ` Kaustabh Chakraborty
2025-09-03 21:59 ` Stephen Rothwell
2025-09-12 2:47 ` Stephen Rothwell
2025-09-28 15:31 ` Kaustabh Chakraborty
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=558A0610.7070405@samsung.com \
--to=inki.dae@samsung.com \
--cc=airlied@linux.ie \
--cc=human.hwang@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sfr@canb.auug.org.au \
/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.