From: kbuild test robot <lkp@intel.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2] omapfb: dss: Handle return error in dss_init_ports.
Date: Thu, 09 Feb 2017 21:05:34 +0000 [thread overview]
Message-ID: <201702100551.GNdbqJ7k%fengguang.wu@intel.com> (raw)
In-Reply-To: <1486634281-10945-1-git-send-email-arvind.yadav.cs@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2262 bytes --]
Hi Arvind,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc7 next-20170209]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Arvind-Yadav/omapfb-dss-Handle-return-error-in-dss_init_ports/20170209-201712
config: arm-omap2plus_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=arm
All error/warnings (new ones prefixed by >>):
drivers/video/fbdev/omap2/omapfb/dss/dss.c: In function 'dss_init_ports':
>> drivers/video/fbdev/omap2/omapfb/dss/dss.c:987:3: error: implicit declaration of function 'dss_uninit_ports' [-Werror=implicit-function-declaration]
dss_uninit_ports(pdev);
^~~~~~~~~~~~~~~~
drivers/video/fbdev/omap2/omapfb/dss/dss.c: At top level:
>> drivers/video/fbdev/omap2/omapfb/dss/dss.c:992:13: warning: conflicting types for 'dss_uninit_ports'
static void dss_uninit_ports(struct platform_device *pdev)
^~~~~~~~~~~~~~~~
>> drivers/video/fbdev/omap2/omapfb/dss/dss.c:992:13: error: static declaration of 'dss_uninit_ports' follows non-static declaration
drivers/video/fbdev/omap2/omapfb/dss/dss.c:987:3: note: previous implicit declaration of 'dss_uninit_ports' was here
dss_uninit_ports(pdev);
^~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/dss_uninit_ports +987 drivers/video/fbdev/omap2/omapfb/dss/dss.c
981 default:
982 break;
983 }
984 } while ((port = omapdss_of_get_next_port(parent, port)) != NULL);
985
986 if (ret)
> 987 dss_uninit_ports(pdev);
988
989 return ret;
990 }
991
> 992 static void dss_uninit_ports(struct platform_device *pdev)
993 {
994 struct device_node *parent = pdev->dev.of_node;
995 struct device_node *port;
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 28765 bytes --]
prev parent reply other threads:[~2017-02-09 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170209095916epcas1p46d7faa4233dfa9b0a0a62aa64c293674@epcas1p4.samsung.com>
2017-02-09 9:59 ` [PATCH v2] omapfb: dss: Handle return error in dss_init_ports Arvind Yadav
2017-02-09 11:22 ` Bartlomiej Zolnierkiewicz
2017-02-09 21:05 ` kbuild test robot [this message]
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=201702100551.GNdbqJ7k%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=linux-fbdev@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