linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hyun Kwon <hyun.kwon@xilinx.com>
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org,
	Michal Simek <monstr@monstr.eu>,
	Wendy Liang <wendy.liang@xilinx.com>
Subject: [xlnx:master 11884/12154] drivers/uio/uio_xilinx_ai_engine.c:39:6: warning: variable 'irq' set but not used
Date: Thu, 22 Apr 2021 18:55:20 +0800	[thread overview]
Message-ID: <202104221814.fACaMPao-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2126 bytes --]

tree:   https://github.com/Xilinx/linux-xlnx master
head:   bcd80b4c331c5d55de978ab0b2f6181a8aea3434
commit: 15d16835418c3d35e07f215d2934dcf9e6725cc6 [11884/12154] uio: Add the UIO driver for AI engine
config: um-allmodconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/Xilinx/linux-xlnx/commit/15d16835418c3d35e07f215d2934dcf9e6725cc6
        git remote add xlnx https://github.com/Xilinx/linux-xlnx
        git fetch --no-tags xlnx master
        git checkout 15d16835418c3d35e07f215d2934dcf9e6725cc6
        # save the attached .config to linux build tree
        make W=1 W=1 ARCH=um 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

   cc1: warning: arch/um/include/uapi: No such file or directory [-Wmissing-include-dirs]
   drivers/uio/uio_xilinx_ai_engine.c: In function 'xilinx_ai_engine_debugfs_write':
>> drivers/uio/uio_xilinx_ai_engine.c:39:6: warning: variable 'irq' set but not used [-Wunused-but-set-variable]
      39 |  int irq, ret;
         |      ^~~

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for MFD_CORE
   Depends on HAS_IOMEM
   Selected by
   - MFD_HI6421_SPMI && STAGING && OF && SPMI
   WARNING: unmet direct dependencies detected for UIO_DMEM_GENIRQ
   Depends on UIO && HAS_DMA
   Selected by
   - UIO_XILINX_AI_ENGINE && UIO


vim +/irq +39 drivers/uio/uio_xilinx_ai_engine.c

    33	
    34	static ssize_t xilinx_ai_engine_debugfs_write(struct file *f,
    35						      const char __user *buf,
    36						      size_t size, loff_t *pos)
    37	{
    38		struct irq_domain *irq_sim_domain = file_inode(f)->i_private;
  > 39		int irq, ret;
    40	
    41		irq = irq_find_mapping(irq_sim_domain, 1);
    42		ret = irq_set_irqchip_state(1, IRQCHIP_STATE_PENDING, true);
    43		if (ret)
    44			return ret;
    45	
    46		return size;
    47	}
    48	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 23671 bytes --]

[-- Attachment #3: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

                 reply	other threads:[~2021-04-22 10:57 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=202104221814.fACaMPao-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hyun.kwon@xilinx.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=monstr@monstr.eu \
    --cc=wendy.liang@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).