From: kernel test robot <lkp@intel.com>
To: "Jim Cromie" <jim.cromie@gmail.com>,
" Łukasz Bartosik" <ukaszb@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jimc:dd-next-2 29/31] lib/dynamic_debug.c:1304:24: sparse: sparse: Using plain integer as NULL pointer
Date: Thu, 01 Jan 2026 04:01:28 +0800 [thread overview]
Message-ID: <202601010356.s9OlXwlF-lkp@intel.com> (raw)
tree: https://github.com/jimc/linux.git dd-next-2
head: a91aa8738cf704e0a0b3137f93bfd3b9bcef20c0
commit: 85feb71d39a764c22e8ef05b1a81b1957736e3ad [29/31] dyndbg: resolve "protection" of class'd pr_debug
config: alpha-randconfig-r133-20251231 (https://download.01.org/0day-ci/archive/20260101/202601010356.s9OlXwlF-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260101/202601010356.s9OlXwlF-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/202601010356.s9OlXwlF-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/dynamic_debug.c:1304:24: sparse: sparse: Using plain integer as NULL pointer
vim +1304 lib/dynamic_debug.c
1296
1297 static struct _ddebug_class_param *
1298 ddebug_get_classmap_kparam(const struct kernel_param *kp,
1299 const struct _ddebug_class_map *map)
1300 {
1301 struct _ddebug_class_param *dcp;
1302
1303 if (kp->ops != ¶m_ops_dyndbg_classes)
> 1304 return false;
1305
1306 dcp = (struct _ddebug_class_param *)kp->arg;
1307
1308 return (map == dcp->map)
1309 ? dcp : (struct _ddebug_class_param *)NULL;
1310 }
1311
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-31 20:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202601010356.s9OlXwlF-lkp@intel.com \
--to=lkp@intel.com \
--cc=jim.cromie@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ukaszb@chromium.org \
/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.