linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Inki Dae <inki.dae@samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: linux-next: build failure after merge of the drm-exynos tree
Date: Mon, 17 Aug 2015 16:08:36 +0900	[thread overview]
Message-ID: <55D18874.6010609@samsung.com> (raw)
In-Reply-To: <20150817155328.1b690385@canb.auug.org.au>

Hi Stephen,

On 2015년 08월 17일 14:53, Stephen Rothwell wrote:
> Hi Inki,
> 
> On Mon, 17 Aug 2015 13:53:42 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> On Mon, 17 Aug 2015 13:51:30 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>>
>>> After merging the drm-exynos tree, today's linux-next build (arm
>>> multi_v7_defconfig) failed like this:
>>>
>>> drivers/gpu/drm/exynos/exynos_mixer.c: In function 'vp_video_buffer':
>>> drivers/gpu/drm/exynos/exynos_mixer.c:395:15: error: 'struct exynos_drm_plane' has no member named 'pixel_format'
>>>   switch (plane->pixel_format) {
>>>                ^
>>> In file included from drivers/gpu/drm/exynos/exynos_mixer.c:17:0:
>>> drivers/gpu/drm/exynos/exynos_mixer.c:404:10: error: 'struct exynos_drm_plane' has no member named 'pixel_format'
>>>      plane->pixel_format);
>>>           ^
>>> include/drm/drmP.h:164:17: note: in definition of macro 'DRM_ERROR'
>>>   drm_err(fmt, ##__VA_ARGS__)
>>>                  ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:411:11: error: 'struct exynos_drm_plane' has no member named 'scan_flag'
>>>   if (plane->scan_flag & DRM_MODE_FLAG_INTERLACE) {
>>>            ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:417:39: error: 'struct exynos_drm_plane' has no member named 'pitch'
>>>     luma_addr[1] = luma_addr[0] + plane->pitch;
>>>                                        ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:418:43: error: 'struct exynos_drm_plane' has no member named 'pitch'
>>>     chroma_addr[1] = chroma_addr[0] + plane->pitch;
>>>                                            ^
>>> In file included from drivers/gpu/drm/exynos/exynos_mixer.c:20:0:
>>> drivers/gpu/drm/exynos/exynos_mixer.c:439:53: error: 'struct exynos_drm_plane' has no member named 'pitch'
>>>   vp_reg_write(res, VP_IMG_SIZE_Y, VP_IMG_HSIZE(plane->pitch) |
>>>                                                      ^
>>> drivers/gpu/drm/exynos/regs-vp.h:59:5: note: in definition of macro 'VP_MASK_VAL'
>>>   (((val) << (low_bit)) & VP_MASK(high_bit, low_bit))
>>>      ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:439:35: note: in expansion of macro 'VP_IMG_HSIZE'
>>>   vp_reg_write(res, VP_IMG_SIZE_Y, VP_IMG_HSIZE(plane->pitch) |
>>>                                    ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:440:21: error: 'struct exynos_drm_plane' has no member named 'fb_height'
>>>    VP_IMG_VSIZE(plane->fb_height));
>>>                      ^
>>> drivers/gpu/drm/exynos/regs-vp.h:59:5: note: in definition of macro 'VP_MASK_VAL'
>>>   (((val) << (low_bit)) & VP_MASK(high_bit, low_bit))
>>>      ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:440:3: note: in expansion of macro 'VP_IMG_VSIZE'
>>>    VP_IMG_VSIZE(plane->fb_height));
>>>    ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:442:53: error: 'struct exynos_drm_plane' has no member named 'pitch'
>>>   vp_reg_write(res, VP_IMG_SIZE_C, VP_IMG_HSIZE(plane->pitch) |
>>>                                                      ^
>>> drivers/gpu/drm/exynos/regs-vp.h:59:5: note: in definition of macro 'VP_MASK_VAL'
>>>   (((val) << (low_bit)) & VP_MASK(high_bit, low_bit))
>>>      ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:442:35: note: in expansion of macro 'VP_IMG_HSIZE'
>>>   vp_reg_write(res, VP_IMG_SIZE_C, VP_IMG_HSIZE(plane->pitch) |
>>>                                    ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:443:21: error: 'struct exynos_drm_plane' has no member named 'fb_height'
>>>    VP_IMG_VSIZE(plane->fb_height / 2));
>>>                      ^
>>> drivers/gpu/drm/exynos/regs-vp.h:59:5: note: in definition of macro 'VP_MASK_VAL'
>>>   (((val) << (low_bit)) & VP_MASK(high_bit, low_bit))
>>>      ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:443:3: note: in expansion of macro 'VP_IMG_VSIZE'
>>>    VP_IMG_VSIZE(plane->fb_height / 2));
>>>    ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:445:39: error: 'struct exynos_drm_plane' has no member named 'src_width'
>>>   vp_reg_write(res, VP_SRC_WIDTH, plane->src_width);
>>>                                        ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:446:40: error: 'struct exynos_drm_plane' has no member named 'src_height'
>>>   vp_reg_write(res, VP_SRC_HEIGHT, plane->src_height);
>>>                                         ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:451:39: error: 'struct exynos_drm_plane' has no member named 'crtc_width'
>>>   vp_reg_write(res, VP_DST_WIDTH, plane->crtc_width);
>>>                                        ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:454:41: error: 'struct exynos_drm_plane' has no member named 'crtc_height'
>>>    vp_reg_write(res, VP_DST_HEIGHT, plane->crtc_height / 2);
>>>                                          ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:457:41: error: 'struct exynos_drm_plane' has no member named 'crtc_height'
>>>    vp_reg_write(res, VP_DST_HEIGHT, plane->crtc_height);
>>>                                          ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:472:27: error: 'struct exynos_drm_plane' has no member named 'mode_height'
>>>   mixer_cfg_scan(ctx, plane->mode_height);
>>>                            ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c:473:30: error: 'struct exynos_drm_plane' has no member named 'mode_height'
>>>   mixer_cfg_rgb_fmt(ctx, plane->mode_height);
>>>                               ^
>>> drivers/gpu/drm/exynos/exynos_mixer.c: In function 'mixer_setup_scale':
>>> drivers/gpu/drm/exynos/exynos_mixer.c:494:11: error: 'const struct exynos_drm_plane' has no member named 'crtc_width
>>
>> Hmm, my message was truncated ...
>>
>> I assume that there was a conflicting change in some other tree, and so
>> have dropped this tree for today (hopefully it will be fixed up soon or
>> you can tell me how to fix this).
> 
> Actually it looks like this was caused by commit
> 
>   a97f353797b4 ("drm/exynos: remove unused fields from struct exynos_drm_plane")
> 
> but only exposed today (maybe by some Kconfig dependency changing so
> that drivers/gpu/drm/exynos/exynos_mixer.c is now built).

I tried to build it with multi_v7_defconfig but I couldn't see any build
error.

Below is commit of linux-next tree I tested,
commit b00278812ebaae29769666ef556abc20a4680581
Merge: ad1d24c c098dc8
Author: Stephen Rothwell <sfr@canb.auug.org.au>
Date:   Fri Aug 14 12:06:53 2015 +1000

    Merge remote-tracking branch 'drm-exynos/exynos-drm/for-next


And today, I re-based exynos-drm/for-next on top of mainline. Could you
update and try to build it again?

Thanks,
Inki Dae

> 

  reply	other threads:[~2015-08-17  7:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17  3:51 linux-next: build failure after merge of the drm-exynos tree Stephen Rothwell
2015-08-17  3:53 ` Stephen Rothwell
2015-08-17  5:53   ` Stephen Rothwell
2015-08-17  7:08     ` Inki Dae [this message]
2015-08-18  3:02       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
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
2015-06-23  1:52 Stephen Rothwell
2015-06-23  5:30 ` Inki Dae
2015-06-24  1:01 ` Stephen Rothwell
2015-06-24  1:21   ` Inki Dae
2015-06-24  1:25     ` Dave Airlie
2015-06-24  1:25     ` Inki Dae

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=55D18874.6010609@samsung.com \
    --to=inki.dae@samsung.com \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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 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).