From: kernel test robot <lkp@intel.com>
To: Pankaj Gupta <pankaj.gupta@nxp.com>, linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
imx@lists.linux.dev, frank.li@nxp.com,
Pankaj Gupta <pankaj.gupta@nxp.com>,
sashiko-bot <sashiko-bot@kernel.org>
Subject: Re: [PATCH -next] firmware: imx: se_ctrl: serialize command receiver registration
Date: Fri, 29 May 2026 10:10:32 +0800 [thread overview]
Message-ID: <202605291047.TLJLq3sB-lkp@intel.com> (raw)
In-Reply-To: <20260528091634.3331090-1-pankaj.gupta@nxp.com>
Hi Pankaj,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20260527]
url: https://github.com/intel-lab-lkp/linux/commits/Pankaj-Gupta/firmware-imx-se_ctrl-serialize-command-receiver-registration/20260528-172942
base: next-20260527
patch link: https://lore.kernel.org/r/20260528091634.3331090-1-pankaj.gupta%40nxp.com
patch subject: [PATCH -next] firmware: imx: se_ctrl: serialize command receiver registration
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20260529/202605291047.TLJLq3sB-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260529/202605291047.TLJLq3sB-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/202605291047.TLJLq3sB-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/firmware/imx/se_ctrl.c:934:4: warning: label at end of compound statement is a C2x extension [-Wc2x-extensions]
934 | }
| ^
1 warning generated.
vim +934 drivers/firmware/imx/se_ctrl.c
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 905
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 906 /* IOCTL entry point of a character device */
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 907 static long se_ioctl(struct file *fp, unsigned int cmd, unsigned long arg)
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 908 {
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 909 struct se_if_device_ctx *dev_ctx = fp->private_data;
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 910 struct se_if_priv *priv = dev_ctx->priv;
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 911 void __user *uarg = (void __user *)arg;
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 912 long err;
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 913
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 914 /* Prevent race during change of device context */
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 915 scoped_cond_guard(mutex_intr, return -EBUSY, &dev_ctx->fops_lock) {
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 916 switch (cmd) {
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 917 case SE_IOCTL_ENABLE_CMD_RCV:
8aff20bcff52903 Pankaj Gupta 2026-05-28 918 scoped_guard(mutex, &priv->priv_dev_ctx->fops_lock) {
8aff20bcff52903 Pankaj Gupta 2026-05-28 919 if (priv->cmd_receiver_clbk_hdl.dev_ctx) {
8aff20bcff52903 Pankaj Gupta 2026-05-28 920 err = -EBUSY;
8aff20bcff52903 Pankaj Gupta 2026-05-28 921 goto out_enable_cmd_rcv;
8aff20bcff52903 Pankaj Gupta 2026-05-28 922 }
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 923 priv->cmd_receiver_clbk_hdl.rx_msg =
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 924 kzalloc(MAX_NVM_MSG_LEN,
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 925 GFP_KERNEL);
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 926 if (!priv->cmd_receiver_clbk_hdl.rx_msg) {
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 927 err = -ENOMEM;
8aff20bcff52903 Pankaj Gupta 2026-05-28 928 goto out_enable_cmd_rcv;
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 929 }
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 930 priv->cmd_receiver_clbk_hdl.rx_msg_sz = MAX_NVM_MSG_LEN;
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 931 priv->cmd_receiver_clbk_hdl.dev_ctx = dev_ctx;
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 932 err = 0;
8aff20bcff52903 Pankaj Gupta 2026-05-28 933 out_enable_cmd_rcv:
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 @934 }
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 935 break;
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 936 case SE_IOCTL_GET_MU_INFO:
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 937 err = se_ioctl_get_mu_info(dev_ctx, uarg);
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 938 break;
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 939 case SE_IOCTL_SETUP_IOBUF:
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 940 err = se_ioctl_setup_iobuf_handler(dev_ctx, uarg);
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 941 break;
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 942 case SE_IOCTL_GET_SOC_INFO:
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 943 err = se_ioctl_get_se_soc_info_handler(dev_ctx, uarg);
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 944 break;
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 945 case SE_IOCTL_CMD_SEND_RCV_RSP:
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 946 err = se_ioctl_cmd_snd_rcv_rsp_handler(dev_ctx, uarg);
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 947 break;
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 948 default:
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 949 err = -EINVAL;
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 950 dev_dbg(priv->dev, "%s: IOCTL %.8x not supported.",
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 951 dev_ctx->devname, cmd);
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 952 }
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 953 }
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 954
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 955 return err;
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 956 }
3ae9dcce8400f0a Pankaj Gupta 2026-01-22 957
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-05-29 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 9:16 Pankaj Gupta
2026-05-29 2:10 ` kernel test robot [this message]
2026-05-29 4:40 ` kernel test robot
2026-05-29 4:40 ` kernel test robot
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=202605291047.TLJLq3sB-lkp@intel.com \
--to=lkp@intel.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pankaj.gupta@nxp.com \
--cc=sashiko-bot@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®