All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Julia Lawall <julia.lawall@inria.fr>
Subject: Re: [RFC PATCH 3/4] drm/i915/writeback: Add some preliminary writeback definitions
Date: Sat, 14 Jun 2025 17:51:25 +0800	[thread overview]
Message-ID: <202506141740.CCj2OXji-lkp@intel.com> (raw)

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20250613061550.2893526-4-suraj.kandpal@intel.com>
References: <20250613061550.2893526-4-suraj.kandpal@intel.com>
TO: Suraj Kandpal <suraj.kandpal@intel.com>

Hi Suraj,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on v6.16-rc1 next-20250613]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Suraj-Kandpal/drm-writeback-Add-function-that-takes-preallocated-connector/20250613-142752
base:   linus/master
patch link:    https://lore.kernel.org/r/20250613061550.2893526-4-suraj.kandpal%40intel.com
patch subject: [RFC PATCH 3/4] drm/i915/writeback: Add some preliminary writeback definitions
:::::: branch date: 27 hours ago
:::::: commit date: 27 hours ago
config: x86_64-randconfig-102-20250614 (https://download.01.org/0day-ci/archive/20250614/202506141740.CCj2OXji-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)

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>
| Reported-by: Julia Lawall <julia.lawall@inria.fr>
| Closes: https://lore.kernel.org/r/202506141740.CCj2OXji-lkp@intel.com/

cocci warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/i915/display/intel_display_device.c:838:2-22: duplicated argument to & or |

vim +838 drivers/gpu/drm/i915/display/intel_display_device.c

785778ce21cf50 Jani Nikula   2024-05-22  816  
69d439818fe501 Matt Roper    2023-05-23  817  #define GEN9_LP_DISPLAY			 \
69d439818fe501 Matt Roper    2023-05-23  818  	.dbuf.slice_mask = BIT(DBUF_S1), \
69d439818fe501 Matt Roper    2023-05-23  819  	.has_dp_mst = 1, \
69d439818fe501 Matt Roper    2023-05-23  820  	.has_ddi = 1, \
69d439818fe501 Matt Roper    2023-05-23  821  	.has_fpga_dbg = 1, \
69d439818fe501 Matt Roper    2023-05-23  822  	.has_hotplug = 1, \
69d439818fe501 Matt Roper    2023-05-23  823  	.has_ipc = 1, \
69d439818fe501 Matt Roper    2023-05-23  824  	.has_psr = 1, \
69d439818fe501 Matt Roper    2023-05-23  825  	.has_psr_hw_tracking = 1, \
69d439818fe501 Matt Roper    2023-05-23  826  	HSW_PIPE_OFFSETS, \
69d439818fe501 Matt Roper    2023-05-23  827  	IVB_CURSOR_OFFSETS, \
69d439818fe501 Matt Roper    2023-05-23  828  	IVB_COLORS, \
69d439818fe501 Matt Roper    2023-05-23  829  	\
69d439818fe501 Matt Roper    2023-05-23  830  	.__runtime_defaults.has_dmc = 1, \
69d439818fe501 Matt Roper    2023-05-23  831  	.__runtime_defaults.has_hdcp = 1, \
69d439818fe501 Matt Roper    2023-05-23  832  	.__runtime_defaults.fbc_mask = BIT(INTEL_FBC_A), \
69d439818fe501 Matt Roper    2023-05-23  833  	.__runtime_defaults.pipe_mask = BIT(PIPE_A) | BIT(PIPE_B) | BIT(PIPE_C), \
69d439818fe501 Matt Roper    2023-05-23  834  	.__runtime_defaults.cpu_transcoder_mask = \
69d439818fe501 Matt Roper    2023-05-23  835  		BIT(TRANSCODER_A) | BIT(TRANSCODER_B) | \
69d439818fe501 Matt Roper    2023-05-23  836  		BIT(TRANSCODER_C) | BIT(TRANSCODER_EDP) | \
2798e4d1ccd9b3 Ville Syrjälä 2023-06-16  837  		BIT(TRANSCODER_DSI_A) | BIT(TRANSCODER_DSI_C), \
ff9a930b83a165 Suraj Kandpal 2025-06-13 @838  		BIT(TRANSCODER_WD_0) | BIT(TRANSCODER_WD_0), \
2798e4d1ccd9b3 Ville Syrjälä 2023-06-16  839  	.__runtime_defaults.port_mask = BIT(PORT_A) | BIT(PORT_B) | BIT(PORT_C)
69d439818fe501 Matt Roper    2023-05-23  840  

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

             reply	other threads:[~2025-06-14  9:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-14  9:51 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-13  6:15 [RFC PATCH 0/4] New Helper to Initialise writeback connector Suraj Kandpal
2025-06-13  6:15 ` [RFC PATCH 3/4] drm/i915/writeback: Add some preliminary writeback definitions Suraj Kandpal

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=202506141740.CCj2OXji-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=julia.lawall@inria.fr \
    --cc=oe-kbuild@lists.linux.dev \
    /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.