All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Umang Jain <umang.jain@ideasonboard.com>,
	linux-media@vger.kernel.org,
	Xavier Roumegue <xavier.roumegue@oss.nxp.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Stefan Klug <stefan.klug@ideasonboard.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>,
	Umang Jain <umang.jain@ideasonboard.com>
Subject: Re: [PATCH] media: dw100: Enable dynamic vertex map
Date: Wed, 23 Oct 2024 07:09:45 +0800	[thread overview]
Message-ID: <202410230647.fPoPRh2O-lkp@intel.com> (raw)
In-Reply-To: <20241022063155.506191-1-umang.jain@ideasonboard.com>

Hi Umang,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linuxtv-media-stage/master]
[also build test WARNING on media-tree/master sailus-media-tree/streams sailus-media-tree/master linus/master v6.12-rc4 next-20241022]
[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/Umang-Jain/media-dw100-Enable-dynamic-vertex-map/20241022-143315
base:   https://git.linuxtv.org/media_stage.git master
patch link:    https://lore.kernel.org/r/20241022063155.506191-1-umang.jain%40ideasonboard.com
patch subject: [PATCH] media: dw100: Enable dynamic vertex map
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20241023/202410230647.fPoPRh2O-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241023/202410230647.fPoPRh2O-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/202410230647.fPoPRh2O-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/media/platform/nxp/dw100/dw100.c:369:3: warning: label followed by a declaration is a C23 extension [-Wc23-extensions]
     369 |                 u32 *user_map = ctrl->p_new.p_u32;
         |                 ^
   1 warning generated.

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for MODVERSIONS
   Depends on [n]: MODULES [=y] && !COMPILE_TEST [=y]
   Selected by [y]:
   - RANDSTRUCT_FULL [=y] && (CC_HAS_RANDSTRUCT [=y] || GCC_PLUGINS [=n]) && MODULES [=y]


vim +369 drivers/media/platform/nxp/dw100/dw100.c

   361	
   362	static int dw100_s_ctrl(struct v4l2_ctrl *ctrl)
   363	{
   364		struct dw100_ctx *ctx =
   365			container_of(ctrl->handler, struct dw100_ctx, hdl);
   366	
   367		switch (ctrl->id) {
   368		case V4L2_CID_DW100_DEWARPING_16x16_VERTEX_MAP:
 > 369			u32 *user_map = ctrl->p_new.p_u32;
   370			unsigned int id;
   371	
   372			mutex_lock(&ctx->maps_mutex);
   373			id = ctx->applied_map_id ? 0 : 1;
   374			memcpy(ctx->maps[id].map, user_map, ctx->map_size);
   375			ctx->user_map_is_updated = true;
   376			mutex_unlock(&ctx->maps_mutex);
   377	
   378			ctx->user_map_is_set = true;
   379			break;
   380		}
   381	
   382		return 0;
   383	}
   384	

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

  reply	other threads:[~2024-10-22 23:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22  6:31 [PATCH] media: dw100: Enable dynamic vertex map Umang Jain
2024-10-22 23:09 ` kernel test robot [this message]
2024-10-26 19:52 ` Xavier Roumegue (OSS)
2024-10-27 14:40   ` Laurent Pinchart
2024-10-28  7:27     ` Umang Jain
2024-10-28 14:32       ` Laurent Pinchart
2024-10-28 14:58         ` Umang Jain
2024-10-28 14:17     ` Umang Jain
2024-10-28 14:41       ` Laurent Pinchart
2024-10-28 15:02         ` Umang Jain
2024-10-28 16:38           ` Laurent Pinchart
2024-10-28  7:32   ` Umang Jain

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=202410230647.fPoPRh2O-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mchehab@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=sakari.ailus@linux.intel.com \
    --cc=stefan.klug@ideasonboard.com \
    --cc=umang.jain@ideasonboard.com \
    --cc=xavier.roumegue@oss.nxp.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.