From: kbuild test robot <lkp@intel.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] staging: sm750fb: Improved coding style
Date: Sun, 12 Mar 2017 21:32:29 +0000 [thread overview]
Message-ID: <201703130517.l7DqNbHg%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170312023402.GA10352@arushi-HP-Pavilion-Notebook>
[-- Attachment #1: Type: text/plain, Size: 1875 bytes --]
Hi Arushi,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.11-rc1 next-20170310]
[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/Arushi-Singhal/staging-sm750fb-Improved-coding-style/20170313-044528
config: x86_64-randconfig-x013-201711 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/staging/sm750fb/ddk750_mode.c: In function 'programModeRegisters':
>> drivers/staging/sm750fb/ddk750_mode.c:155:106: error: 'pvssm' undeclared (first use in this function)
poke32(pvs, ((pModeParam->vertical_sync_height << PANEL_VERTICAL_SYNC_HEIGHT_SHIFT) & pvshm) | (pvss & pvssm));
^~~~~
drivers/staging/sm750fb/ddk750_mode.c:155:106: note: each undeclared identifier is reported only once for each function it appears in
vim +/pvssm +155 drivers/staging/sm750fb/ddk750_mode.c
149 poke32(pht, reg);
150
151 poke32(phs, ((pModeParam->horizontal_sync_width << PANEL_HORIZONTAL_SYNC_WIDTH_SHIFT) & phswm) | (phss & phssm));
152
153 poke32(pvt, (((pModeParam->vertical_total - 1) << PANEL_VERTICAL_TOTAL_TOTAL_SHIFT) & pvttm) | (pvde & pvtdem));
154
> 155 poke32(pvs, ((pModeParam->vertical_sync_height << PANEL_VERTICAL_SYNC_HEIGHT_SHIFT) & pvshm) | (pvss & pvssm));
156
157 tmp = DISPLAY_CTRL_TIMING | DISPLAY_CTRL_PLANE;
158 if (pModeParam->vertical_sync_polarity)
---
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: 27281 bytes --]
prev parent reply other threads:[~2017-03-12 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 2:46 [PATCH] staging: sm750fb: Improved coding style Arushi Singhal
2017-03-12 4:46 ` Greg Kroah-Hartman
2017-03-12 21:32 ` 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=201703130517.l7DqNbHg%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