From: kbuild test robot <lkp@intel.com>
To: "Geyslan G. Bem" <geyslan@gmail.com>
Cc: kbuild-all@01.org, peter.senna@gmail.com,
"Geyslan G. Bem" <geyslan@gmail.com>,
Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] usb: host: ehci.h: remove duplicated return
Date: Thu, 10 Dec 2015 05:08:07 +0800 [thread overview]
Message-ID: <201512100405.Pm8ylKOF%fengguang.wu@intel.com> (raw)
In-Reply-To: <1449691056-32238-3-git-send-email-geyslan@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1732 bytes --]
Hi Geyslan,
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v4.4-rc4 next-20151209]
url: https://github.com/0day-ci/linux/commits/Geyslan-G-Bem/usb-host-ehci-h-cleanup-header-file/20151210-040115
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
config: x86_64-randconfig-s3-12100340 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
In file included from drivers/usb/host/ehci-hcd.c:109:0:
drivers/usb/host/ehci.h: In function 'ehci_port_speed':
>> drivers/usb/host/ehci.h:668:3: error: label at end of compound statement
default:
^
vim +668 drivers/usb/host/ehci.h
^1da177e Linus Torvalds 2005-04-16 662 case 0:
^1da177e Linus Torvalds 2005-04-16 663 return 0;
^1da177e Linus Torvalds 2005-04-16 664 case 1:
288ead45 Alan Stern 2010-03-04 665 return USB_PORT_STAT_LOW_SPEED;
^1da177e Linus Torvalds 2005-04-16 666 case 2:
50691528 Geyslan G. Bem 2015-12-09 667 /* fall through to default function return */
^1da177e Linus Torvalds 2005-04-16 @668 default:
^1da177e Linus Torvalds 2005-04-16 669 }
^1da177e Linus Torvalds 2005-04-16 670 }
288ead45 Alan Stern 2010-03-04 671 return USB_PORT_STAT_HIGH_SPEED;
:::::: The code at line 668 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 27024 bytes --]
next prev parent reply other threads:[~2015-12-09 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 19:57 [PATCH 1/4] usb: host: ehci.h: cleanup header file Geyslan G. Bem
2015-12-09 19:57 ` [PATCH 2/4] " Geyslan G. Bem
2015-12-09 20:11 ` Sergei Shtylyov
2015-12-09 20:18 ` Geyslan G. Bem
2015-12-09 19:57 ` [PATCH 3/4] usb: host: ehci.h: remove duplicated return Geyslan G. Bem
2015-12-09 20:10 ` Sergei Shtylyov
2015-12-09 20:15 ` Geyslan G. Bem
2015-12-09 20:22 ` Greg Kroah-Hartman
2015-12-09 20:22 ` Sergei Shtylyov
2015-12-09 21:08 ` kbuild test robot [this message]
2015-12-09 21:24 ` kbuild test robot
2015-12-09 21:47 ` Geyslan G. Bem
2015-12-09 19:57 ` [PATCH 4/4] usb: host: ehci.h: use flexible array instead of zero-length array Geyslan G. Bem
2015-12-09 20:09 ` [PATCH 1/4] usb: host: ehci.h: cleanup header file Greg Kroah-Hartman
2015-12-09 21:00 ` Geyslan G. Bem
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=201512100405.Pm8ylKOF%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=geyslan@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.senna@gmail.com \
--cc=stern@rowland.harvard.edu \
/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®