Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: "Jeffrey Hugo" <quic_jhugo@quicinc.com>,
	"Jouni Högander" <jouni.hogander@intel.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	joonas.lahtinen@linux.intel.com,
	"Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
	"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>
Subject: Re: i915 build error on drm-misc-next
Date: Fri, 23 Feb 2024 14:35:05 -0500	[thread overview]
Message-ID: <ZdjzaesUVxF-V5qQ@intel.com> (raw)
In-Reply-To: <6ee1af5a-413c-1c09-5234-ceb8d8e605ad@quicinc.com>

On Fri, Feb 23, 2024 at 09:47:11AM -0800, Abhinav Kumar wrote:
> CC Dmitry
> 
> Hi Rodrigo
> 
> On 2/23/2024 9:00 AM, Rodrigo Vivi wrote:
> > On Fri, Feb 23, 2024 at 08:50:06AM -0700, Jeffrey Hugo wrote:
> > > With the x86_64_defconfig I see the following when building drm-misc-next:
> > > 
> > >    CC      drivers/gpu/drm/i915/display/intel_crt.o
> > >    CC      drivers/gpu/drm/i915/display/intel_cx0_phy.o
> > >    CC      drivers/gpu/drm/i915/display/intel_ddi.o
> > >    CC      drivers/gpu/drm/i915/display/intel_ddi_buf_trans.o
> > >    CC      drivers/gpu/drm/i915/display/intel_display_device.o
> > >    CC      drivers/gpu/drm/i915/display/intel_display_trace.o
> > >    CC      drivers/gpu/drm/i915/display/intel_dkl_phy.o
> > >    CC      drivers/gpu/drm/i915/display/intel_dp.o
> > >    CC      drivers/gpu/drm/i915/display/intel_dp_aux.o
> > >    CC      drivers/gpu/drm/i915/display/intel_dp_aux_backlight.o
> > >    CC      drivers/gpu/drm/i915/display/intel_dp_hdcp.o
> > >    CC      drivers/gpu/drm/i915/display/intel_dp_link_training.o
> > >    CC      drivers/gpu/drm/i915/display/intel_dp_mst.o
> > >    CC      drivers/gpu/drm/i915/display/intel_dsi.o
> > >    CC      drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.o
> > >    CC      drivers/gpu/drm/i915/display/intel_dsi_vbt.o
> > >    CC      drivers/gpu/drm/i915/display/intel_dvo.o
> > >    CC      drivers/gpu/drm/i915/display/intel_gmbus.o
> > >    CC      drivers/gpu/drm/i915/display/intel_hdmi.o
> > >    CC      drivers/gpu/drm/i915/display/intel_lspcon.o
> > >    CC      drivers/gpu/drm/i915/display/intel_lvds.o
> > >    CC      drivers/gpu/drm/i915/display/intel_panel.o
> > >    CC      drivers/gpu/drm/i915/display/intel_pps.o
> > > drivers/gpu/drm/i915/display/intel_dp.c: In function
> > > ‘intel_write_dp_vsc_sdp’:
> > > drivers/gpu/drm/i915/display/intel_dp.c:4232:15: error: implicit declaration
> > > of function ‘intel_dp_vsc_sdp_pack’; did you mean ‘drm_dp_vsc_sdp_pack’?
> > > [-Werror=implicit-function-declaration]
> > >   4232 |         len = intel_dp_vsc_sdp_pack(vsc, &sdp, sizeof(sdp));
> > >        |               ^~~~~~~~~~~~~~~~~~~~~
> > >        |               drm_dp_vsc_sdp_pack
> > > 
> > > Is this a known issue?
> > 
> > o.O - what a mistery!
> > 
> > it looks that drm-misc-next has only part of the patch:
> > 31a5b6ed88c7 ("drm/i915/display: Unify VSC SPD preparation")
> > 
> > without the patch itself...
> > 
> > I couldn't even trace back to understand how the declaration is
> > gone from the drm-misc-next...
> > 
> 
> Looks like the issue here is that the below patch which landed in
> drm-misc-next
> 
> https://patchwork.freedesktop.org/patch/579128/?series=130145&rev=1
> 
> was based on top of drm-tip because the intel CI runs on drm-tip and not
> drm-misc-next.
> 
> But, https://patchwork.freedesktop.org/patch/572622/ is not present in
> drm-misc-next.
> 
> Hence this broke the compilation.
> 
> How would you prefer to fix this? We revert
> https://patchwork.freedesktop.org/series/130145/ from drm-misc and land it
> through i915 tree and can you provide us a tag from the i915 tree to rebase
> our msm-next tree on?

The revert from drm-misc is a possibility, then you squash
https://lore.kernel.org/all/20240223191548.392185-1-rodrigo.vivi@intel.com/
in and merge it again.

or if drm-misc and drm maintainers are okay we can simply add
https://lore.kernel.org/all/20240223191548.392185-1-rodrigo.vivi@intel.com/
on top of drm-misc-next

and on any conflict later the resolution is simply deleting this line
anyway.

> 
> > > 
> > > -Jeff

  reply	other threads:[~2024-02-23 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 15:50 i915 build error on drm-misc-next Jeffrey Hugo
2024-02-23 17:00 ` Rodrigo Vivi
2024-02-23 17:47   ` Abhinav Kumar
2024-02-23 19:35     ` Rodrigo Vivi [this message]
2024-02-23 20:18       ` Abhinav Kumar

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=ZdjzaesUVxF-V5qQ@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=jouni.hogander@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=quic_jhugo@quicinc.com \
    --cc=tvrtko.ursulin@linux.intel.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