public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ong Hean Loong <hean.loong.ong@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Dinh Nguyen <dinh.nguyen@intel.com>
Subject: [dinguyen:socfpga-5.14_v1 31/121] drivers/video/fbdev/altvipfb2-plat.c:88:13: warning: variable 'retval' set but not used
Date: Fri, 5 Nov 2021 21:13:00 +0800	[thread overview]
Message-ID: <202111052153.Vpbb86Qv-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git socfpga-5.14_v1
head:   cc7ba8d9b34b85acfbeefb77fa57c116c733c2c4
commit: 624fd922941d21e091defb0714379abba1d64cab [31/121] FogBugz #421702-2: implement Frame Buffer II for Display Port IP
config: mips-allyesconfig (attached as .config)
compiler: mips-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git/commit/?id=624fd922941d21e091defb0714379abba1d64cab
        git remote add dinguyen https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git
        git fetch --no-tags dinguyen socfpga-5.14_v1
        git checkout 624fd922941d21e091defb0714379abba1d64cab
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=mips 

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 >>):

   drivers/video/fbdev/altvipfb2-plat.c: In function 'altvipfb2_plat_probe':
>> drivers/video/fbdev/altvipfb2-plat.c:88:13: warning: variable 'retval' set but not used [-Wunused-but-set-variable]
      88 |         int retval;
         |             ^~~~~~


vim +/retval +88 drivers/video/fbdev/altvipfb2-plat.c

    85	
    86	static int altvipfb2_plat_probe(struct platform_device *pdev)
    87	{
  > 88		int retval;
    89	
    90		struct device *dev = &pdev->dev;
    91		struct resource *reg_res;
    92		struct altvipfb2_priv *fbdev;
    93	
    94		fbdev = devm_kzalloc(dev, sizeof(*fbdev), GFP_KERNEL);
    95		if (!fbdev)
    96			return -ENOMEM;
    97	
    98		reg_res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
    99		if (!reg_res)
   100			return -ENODEV;
   101	
   102		fbdev->base = devm_ioremap_resource(dev, reg_res);
   103		if (IS_ERR(fbdev->base)) {
   104			dev_err(dev, "devm_ioremap_resource failed\n");
   105			retval = PTR_ERR(fbdev->base);
   106			return -ENOMEM;
   107		}
   108	
   109		altvipfb2_of_setup(fbdev, pdev);
   110	
   111		platform_set_drvdata(pdev, fbdev);
   112	
   113		return altvipfb2_probe(dev, fbdev->base);
   114	}
   115	

---
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: 71063 bytes --]

                 reply	other threads:[~2021-11-05 13:14 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=202111052153.Vpbb86Qv-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dinh.nguyen@intel.com \
    --cc=hean.loong.ong@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.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