All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Harry Wentland <harry.wentland@amd.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH v2 07/17] drm/colorop: Introduce new drm_colorop mode object
Date: Sat, 21 Oct 2023 12:13:49 +0800	[thread overview]
Message-ID: <202310211231.WlOSaCad-lkp@intel.com> (raw)
In-Reply-To: <20231019212133.245155-8-harry.wentland@amd.com>

Hi Harry,

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

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm/drm-next drm-exynos/exynos-drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.6-rc6 next-20231020]
[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/Harry-Wentland/drm-atomic-Allow-get_value-for-immutable-properties-on-atomic-drivers/20231020-052542
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:    https://lore.kernel.org/r/20231019212133.245155-8-harry.wentland%40amd.com
patch subject: [RFC PATCH v2 07/17] drm/colorop: Introduce new drm_colorop mode object
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20231021/202310211231.WlOSaCad-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231021/202310211231.WlOSaCad-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/202310211231.WlOSaCad-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/drm_colorop.c:59:6: warning: no previous prototype for '__drm_atomic_helper_colorop_duplicate_state' [-Wmissing-prototypes]
      59 | void __drm_atomic_helper_colorop_duplicate_state(struct drm_colorop *colorop,
         |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/gpu/drm/drm_colorop.c:95:6: warning: no previous prototype for '__drm_colorop_destroy_state' [-Wmissing-prototypes]
      95 | void __drm_colorop_destroy_state(struct drm_colorop_state *state)
         |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/gpu/drm/drm_colorop.c:108:6: warning: no previous prototype for 'drm_colorop_destroy_state' [-Wmissing-prototypes]
     108 | void drm_colorop_destroy_state(struct drm_colorop *colorop,
         |      ^~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/gpu/drm/drm_colorop.c:123:6: warning: no previous prototype for '__drm_colorop_state_reset' [-Wmissing-prototypes]
     123 | void __drm_colorop_state_reset(struct drm_colorop_state *colorop_state,
         |      ^~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/gpu/drm/drm_colorop.c:142:6: warning: no previous prototype for '__drm_colorop_reset' [-Wmissing-prototypes]
     142 | void __drm_colorop_reset(struct drm_colorop *colorop,
         |      ^~~~~~~~~~~~~~~~~~~


vim +/__drm_atomic_helper_colorop_duplicate_state +59 drivers/gpu/drm/drm_colorop.c

    58	
  > 59	void __drm_atomic_helper_colorop_duplicate_state(struct drm_colorop *colorop,
    60							 struct drm_colorop_state *state)
    61	{
    62		memcpy(state, colorop->state, sizeof(*state));
    63	}
    64	
    65	struct drm_colorop_state *
    66	drm_atomic_helper_colorop_duplicate_state(struct drm_colorop *colorop)
    67	{
    68		struct drm_colorop_state *state;
    69	
    70		if (WARN_ON(!colorop->state))
    71			return NULL;
    72	
    73		state = kmalloc(sizeof(*state), GFP_KERNEL);
    74		if (state)
    75			__drm_atomic_helper_colorop_duplicate_state(colorop, state);
    76	
    77		return state;
    78	}
    79	
    80	
    81	void drm_colorop_atomic_destroy_state(struct drm_colorop *colorop,
    82					      struct drm_colorop_state *state)
    83	{
    84		kfree(state);
    85	}
    86	
    87	/**
    88	 * __drm_colorop_destroy_state - release colorop state
    89	 * @state: colorop state object to release
    90	 *
    91	 * Releases all resources stored in the colorop state without actually freeing
    92	 * the memory of the colorop state. This is useful for drivers that subclass the
    93	 * colorop state.
    94	 */
  > 95	void __drm_colorop_destroy_state(struct drm_colorop_state *state)
    96	{
    97		/* TODO might need this later */
    98	}
    99	
   100	/**
   101	 * drm_colorop_destroy_state - default state destroy hook
   102	 * @colorop: drm colorop
   103	 * @state: colorop state object to release
   104	 *
   105	 * Default colorop state destroy hook for drivers which don't have their own
   106	 * subclassed colorop state structure.
   107	 */
 > 108	void drm_colorop_destroy_state(struct drm_colorop *colorop,
   109						   struct drm_colorop_state *state)
   110	{
   111		kfree(state);
   112	}
   113	EXPORT_SYMBOL(drm_colorop_destroy_state);
   114	
   115	/**
   116	 * __drm_colorop_state_reset - resets colorop state to default values
   117	 * @colorop_state: atomic colorop state, must not be NULL
   118	 * @colorop: colorop object, must not be NULL
   119	 *
   120	 * Initializes the newly allocated @colorop_state with default
   121	 * values. This is useful for drivers that subclass the CRTC state.
   122	 */
 > 123	void __drm_colorop_state_reset(struct drm_colorop_state *colorop_state,
   124						   struct drm_colorop *colorop)
   125	{
   126		colorop_state->colorop = colorop;
   127	}
   128	EXPORT_SYMBOL(__drm_colorop_state_reset);
   129	
   130	/**
   131	 * __drm_colorop_reset - reset state on colorop
   132	 * @colorop: drm colorop
   133	 * @colorop_state: colorop state to assign
   134	 *
   135	 * Initializes the newly allocated @colorop_state and assigns it to
   136	 * the &drm_crtc->state pointer of @colorop, usually required when
   137	 * initializing the drivers or when called from the &drm_colorop_funcs.reset
   138	 * hook.
   139	 *
   140	 * This is useful for drivers that subclass the colorop state.
   141	 */
 > 142	void __drm_colorop_reset(struct drm_colorop *colorop,
   143					     struct drm_colorop_state *colorop_state)
   144	{
   145		if (colorop_state)
   146			__drm_colorop_state_reset(colorop_state, colorop);
   147	
   148		colorop->state = colorop_state;
   149	}
   150	

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

  reply	other threads:[~2023-10-21  4:14 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19 21:21 [RFC PATCH v2 00/17] Color Pipeline API w/ VKMS Harry Wentland
2023-10-19 21:21 ` [RFC PATCH v2 01/17] drm/atomic: Allow get_value for immutable properties on atomic drivers Harry Wentland
2023-10-19 21:21 ` [RFC PATCH v2 02/17] drm: Don't treat 0 as -1 in drm_fixp2int_ceil Harry Wentland
2023-10-19 21:21 ` [RFC PATCH v2 03/17] drm/vkms: Create separate Kconfig file for VKMS Harry Wentland
2023-10-19 21:21 ` [RFC PATCH v2 04/17] drm/vkms: Add kunit tests for VKMS LUT handling Harry Wentland
2023-10-23 22:34   ` Arthur Grillo
2023-10-19 21:21 ` [RFC PATCH v2 05/17] drm/vkms: Avoid reading beyond LUT array Harry Wentland
2023-10-30 13:29   ` Pekka Paalanen
2023-11-06 20:48     ` Harry Wentland
2023-10-19 21:21 ` [RFC PATCH v2 06/17] drm/doc/rfc: Describe why prescriptive color pipeline is needed Harry Wentland
2023-10-20 14:22   ` Sebastian Wick
2023-10-20 14:57     ` Pekka Paalanen
2023-10-20 15:23       ` Harry Wentland
2023-10-23  8:12         ` Pekka Paalanen
2023-10-25 20:16           ` Alex Goins
2023-10-26  8:57             ` Pekka Paalanen
2023-10-26 17:30               ` Sebastian Wick
2023-10-26 19:25                 ` Alex Goins
2023-10-27  8:59                   ` Michel Dänzer
2023-10-27 10:01                     ` Sebastian Wick
2023-10-27 12:01                       ` Pekka Paalanen
2023-11-04 23:01                   ` Christopher Braga
2023-11-07 16:52                     ` Harry Wentland
2023-11-07 16:52                   ` Harry Wentland
2023-11-07 16:52                 ` Harry Wentland
2023-11-07 21:17                   ` Sebastian Wick
2023-11-07 16:52               ` Harry Wentland
2023-11-07 16:52             ` Harry Wentland
2023-11-08 12:18   ` Shankar, Uma
2023-11-08 13:43     ` Joshua Ashton
2023-11-09 10:17       ` Shankar, Uma
2023-11-09 11:55         ` Pekka Paalanen
2023-11-10 11:27           ` Shankar, Uma
2023-11-10 13:27             ` Pekka Paalanen
2023-11-08 14:37     ` Harry Wentland
2023-11-09 10:24       ` Shankar, Uma
2023-10-19 21:21 ` [RFC PATCH v2 07/17] drm/colorop: Introduce new drm_colorop mode object Harry Wentland
2023-10-21  4:13   ` kernel test robot [this message]
2023-10-19 21:21 ` [RFC PATCH v2 08/17] drm/colorop: Add TYPE property Harry Wentland
2023-10-21  9:04   ` kernel test robot
2023-10-19 21:21 ` [RFC PATCH v2 09/17] drm/color: Add 1D Curve subtype Harry Wentland
2023-10-19 21:21 ` [RFC PATCH v2 10/17] drm/colorop: Add BYPASS property Harry Wentland
2023-10-19 21:21 ` [RFC PATCH v2 11/17] drm/colorop: Add NEXT property Harry Wentland
2023-10-19 21:21 ` [RFC PATCH v2 12/17] drm/colorop: Add atomic state print for drm_colorop Harry Wentland
2023-10-19 21:21 ` [RFC PATCH v2 13/17] drm/colorop: Add new IOCTLs to retrieve drm_colorop objects Harry Wentland
2023-10-19 21:21 ` [RFC PATCH v2 14/17] drm/plane: Add COLOR PIPELINE property Harry Wentland
2023-10-20  0:15   ` kernel test robot
2023-10-19 21:21 ` [RFC PATCH v2 15/17] drm/colorop: Add NEXT to colorop state print Harry Wentland
2023-10-19 21:21 ` [RFC PATCH v2 16/17] drm/vkms: Add enumerated 1D curve colorop Harry Wentland
2023-10-19 21:21 ` [RFC PATCH v2 17/17] drm/vkms: Add kunit tests for linear and sRGB LUTs Harry Wentland
2023-11-08 11:54 ` [RFC PATCH v2 00/17] Color Pipeline API w/ VKMS Shankar, Uma
2023-11-08 14:32   ` Harry Wentland

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=202310211231.WlOSaCad-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=harry.wentland@amd.com \
    --cc=oe-kbuild-all@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.