linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Jaroslav Resler <resler@cs.cas.cz>
Cc: kernel-janitors@vger.kernel.org,
	Gustavo Padovan <gustavo.padovan@collabora.co.uk>,
	"Cho, Yu-Chen" <acho@suse.com>,
	linux-bluetooth@vger.kernel.org
Subject: [bluetooth:master 22/22] drivers/bluetooth/btusb.c:97:2: error: expected '}' before '{' token
Date: Wed, 19 Sep 2012 08:06:57 +0800	[thread overview]
Message-ID: <20120919000657.GA9208@localhost> (raw)

Hi Jaroslav,

FYI, kernel build failed on

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
head:   493969cf4728668412ecd428a60b39914d9831e3
commit: 493969cf4728668412ecd428a60b39914d9831e3 [22/22] Bluetooth: Add support for BCM20702A0 [04ca, 2003]
config: x86_64-allmodconfig

All related error/warning messages:

drivers/bluetooth/btusb.c:97:2: error: expected '}' before '{' token

vim +97 drivers/bluetooth/btusb.c
    92		/* Canyon CN-BTU1 with HID interfaces */
    93		{ USB_DEVICE(0x0c10, 0x0000) },
    94	
    95		/* Broadcom BCM20702A0 */
    96		{ USB_DEVICE(0x04ca, 0x2003) }
  > 97		{ USB_DEVICE(0x0489, 0xe042) },
    98		{ USB_DEVICE(0x0a5c, 0x21e3) },
    99		{ USB_DEVICE(0x0a5c, 0x21e6) },
   100		{ USB_DEVICE(0x0a5c, 0x21e8) },
   101		{ USB_DEVICE(0x0a5c, 0x21f3) },
   102		{ USB_DEVICE(0x413c, 0x8197) },

---
0-DAY kernel build testing backend         Open Source Technology Centre
Fengguang Wu, Yuanhan Liu                              Intel Corporation

             reply	other threads:[~2012-09-19  0:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19  0:06 Fengguang Wu [this message]
2012-09-19  1:06 ` [bluetooth:master 22/22] drivers/bluetooth/btusb.c:97:2: error: expected '}' before '{' token Gustavo Padovan
2012-09-19  4:20   ` Al Cho

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=20120919000657.GA9208@localhost \
    --to=fengguang.wu@intel.com \
    --cc=acho@suse.com \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=resler@cs.cas.cz \
    /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;
as well as URLs for NNTP newsgroup(s).