From: kbuild test robot <lkp@intel.com>
To: Walt Feasel <waltfeasel@gmail.com>
Cc: kbuild-all@01.org, w.d.hubbs@gmail.com,
devel@driverdev.osuosl.org, kirk@reisers.ca,
Walt Feasel <waltfeasel@gmail.com>,
gregkh@linuxfoundation.org, speakup@linux-speakup.org,
linux-kernel@vger.kernel.org, samuel.thibault@ens-lyon.org,
chris@the-brannons.com
Subject: Re: [PATCH v2 1/5] staging: speakup: synth.c Spaces around operators
Date: Sun, 20 Nov 2016 02:48:34 +0800 [thread overview]
Message-ID: <201611200258.LVHsOkfg%fengguang.wu@intel.com> (raw)
In-Reply-To: <1479576947-3605-2-git-send-email-waltfeasel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]
Hi Walt,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.9-rc5 next-20161117]
[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/Walt-Feasel/staging-speakup-synth-c-checkpatch-modifications/20161120-013925
config: openrisc-allmodconfig (attached as .config)
compiler: or32-linux-gcc (GCC) 4.5.1-or32-1.0rc1
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=openrisc
All errors (new ones prefixed by >>):
drivers/staging/speakup/synth.c:1:1: error: stray '#' in program
>> drivers/staging/speakup/synth.c:1:3: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'include'
In file included from drivers/staging/speakup/synth.c:2:0:
include/linux/ctype.h: In function '__tolower':
include/linux/ctype.h:43:6: error: '_ctype' undeclared (first use in this function)
include/linux/ctype.h:43:6: note: each undeclared identifier is reported only once for each function it appears in
include/linux/ctype.h: In function '__toupper':
include/linux/ctype.h:50:6: error: '_ctype' undeclared (first use in this function)
vim +1 drivers/staging/speakup/synth.c
> 1 w#include <linux/types.h>
2 #include <linux/ctype.h> /* for isdigit() and friends */
3 #include <linux/fs.h>
4 #include <linux/mm.h> /* for verify_area */
---
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: 39339 bytes --]
next prev parent reply other threads:[~2016-11-19 18:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 17:35 [PATCH v2 0/5] staging: speakup: synth.c checkpatch modifications Walt Feasel
2016-11-19 17:35 ` [PATCH v2 1/5] staging: speakup: synth.c Spaces around operators Walt Feasel
2016-11-19 18:06 ` kbuild test robot
2016-11-19 18:48 ` kbuild test robot [this message]
2016-11-19 19:34 ` [PATCH v3 " Walt Feasel
2016-11-25 13:10 ` [PATCH v2 " Dan Carpenter
2016-11-19 17:35 ` [PATCH v2 2/5] staging: speakup: synth.c Blank line before } Walt Feasel
2016-11-19 17:35 ` [PATCH v2 3/5] staging: speakup: synth.c Logical continuation Walt Feasel
2016-11-19 17:35 ` [PATCH v2 4/5] staging: speakup: synth.c Comment modifications Walt Feasel
2016-11-19 17:35 ` [PATCH v2 5/5] staging: speakup: synth.c Align parenthesis Walt Feasel
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=201611200258.LVHsOkfg%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.org \
--cc=w.d.hubbs@gmail.com \
--cc=waltfeasel@gmail.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
all inboxes | Powered by JetHome®