All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>, intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, oe-kbuild-all@lists.linux.dev
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915/hdcp: Move common message filling function to its own file
Date: Wed, 20 Sep 2023 17:30:15 +0800	[thread overview]
Message-ID: <202309201747.5tql4Gr4-lkp@intel.com> (raw)
In-Reply-To: <20230920063611.242942-3-suraj.kandpal@intel.com>

Hi Suraj,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-tip/drm-tip]

url:    https://github.com/intel-lab-lkp/linux/commits/Suraj-Kandpal/drm-i915-hdcp-Move-checks-for-gsc-health-status/20230920-143839
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:    https://lore.kernel.org/r/20230920063611.242942-3-suraj.kandpal%40intel.com
patch subject: [Intel-gfx] [PATCH 2/2] drm/i915/hdcp: Move common message filling function to its own file
config: i386-buildonly-randconfig-002-20230920 (https://download.01.org/0day-ci/archive/20230920/202309201747.5tql4Gr4-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230920/202309201747.5tql4Gr4-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309201747.5tql4Gr4-lkp@intel.com/

All errors (new ones prefixed by >>):

>> make[7]: *** No rule to make target 'drivers/gpu/drm/i915/display/intel_hdcp_gsc_message.o', needed by 'drivers/gpu/drm/i915/i915.o'.
   make[7]: *** [scripts/Makefile.build:243: drivers/gpu/drm/i915/display/intel_hdcp_gsc.o] Error 1 shuffle=1704323870
   make[7]: Target 'drivers/gpu/drm/i915/' not remade because of errors.

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>, intel-gfx@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev, jani.nikula@intel.com
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915/hdcp: Move common message filling function to its own file
Date: Wed, 20 Sep 2023 17:30:15 +0800	[thread overview]
Message-ID: <202309201747.5tql4Gr4-lkp@intel.com> (raw)
In-Reply-To: <20230920063611.242942-3-suraj.kandpal@intel.com>

Hi Suraj,

kernel test robot noticed the following build errors:

[auto build test ERROR on drm-tip/drm-tip]

url:    https://github.com/intel-lab-lkp/linux/commits/Suraj-Kandpal/drm-i915-hdcp-Move-checks-for-gsc-health-status/20230920-143839
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:    https://lore.kernel.org/r/20230920063611.242942-3-suraj.kandpal%40intel.com
patch subject: [Intel-gfx] [PATCH 2/2] drm/i915/hdcp: Move common message filling function to its own file
config: i386-buildonly-randconfig-002-20230920 (https://download.01.org/0day-ci/archive/20230920/202309201747.5tql4Gr4-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230920/202309201747.5tql4Gr4-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309201747.5tql4Gr4-lkp@intel.com/

All errors (new ones prefixed by >>):

>> make[7]: *** No rule to make target 'drivers/gpu/drm/i915/display/intel_hdcp_gsc_message.o', needed by 'drivers/gpu/drm/i915/i915.o'.
   make[7]: *** [scripts/Makefile.build:243: drivers/gpu/drm/i915/display/intel_hdcp_gsc.o] Error 1 shuffle=1704323870
   make[7]: Target 'drivers/gpu/drm/i915/' not remade because of errors.

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2023-09-20  9:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20  6:36 [Intel-gfx] [PATCH 0/2] Refactor i915 HDCP for XE Suraj Kandpal
2023-09-20  6:36 ` [Intel-gfx] [PATCH 1/2] drm/i915/hdcp: Move checks for gsc health status Suraj Kandpal
2023-10-09  9:06   ` Shankar, Uma
2023-09-20  6:36 ` [Intel-gfx] [PATCH 2/2] drm/i915/hdcp: Move common message filling function to its own file Suraj Kandpal
2023-09-20  8:46   ` kernel test robot
2023-09-20  8:46     ` kernel test robot
2023-09-20  8:50   ` Suraj Kandpal
2023-09-20  9:13     ` Jani Nikula
2023-09-20  9:29       ` Kandpal, Suraj
2023-09-20 10:38     ` [Intel-gfx] [PATCH v3 " Suraj Kandpal
2023-09-20 12:09       ` Jani Nikula
2023-09-20 15:57         ` Kandpal, Suraj
2023-09-21  5:38       ` [Intel-gfx] [PATCH v4 " Suraj Kandpal
2023-10-09  9:14         ` Shankar, Uma
2023-09-20  9:30   ` kernel test robot [this message]
2023-09-20  9:30     ` [Intel-gfx] [PATCH " kernel test robot
2023-09-21 15:32   ` kernel test robot
2023-09-21 15:32     ` kernel test robot
2023-09-20  7:05 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Refactor i915 HDCP for XE Patchwork
2023-09-20  9:28 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Refactor i915 HDCP for XE (rev2) Patchwork
2023-09-20  9:28 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-09-20  9:46 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-09-20 13:02 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Refactor i915 HDCP for XE (rev3) Patchwork
2023-09-20 13:02 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-09-20 13:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-09-20 18:19 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-21  7:04 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Refactor i915 HDCP for XE (rev4) Patchwork
2023-09-21  7:04 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-09-21  7:22 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork

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=202309201747.5tql4Gr4-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=suraj.kandpal@intel.com \
    /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.