From: David Miller <davem@davemloft.net>
To: fengguang.wu@intel.com
Cc: oneukum@suse.com, kbuild-all@01.org, netdev@vger.kernel.org
Subject: Re: [net-next:master 6/12] include/linux/usb/cdc.h:23: error: redefinition of 'struct usb_cdc_parsed_header'
Date: Tue, 15 Sep 2015 13:27:42 -0700 (PDT) [thread overview]
Message-ID: <20150915.132742.739418011603329556.davem@davemloft.net> (raw)
In-Reply-To: <201509160310.FiynyPOo%fengguang.wu@intel.com>
From: kbuild test robot <fengguang.wu@intel.com>
Date: Wed, 16 Sep 2015 03:57:11 +0800
> All error/warnings (new ones prefixed by >>):
>
> In file included from drivers/usb/gadget/function/u_ether.h:20,
> from drivers/usb/gadget/legacy/cdc2.c:16:
> include/linux/usb/cdc.h:47: warning: 'struct usb_interface' declared inside parameter list
> include/linux/usb/cdc.h:47: warning: its scope is only this definition or declaration, which is probably not what you want
> In file included from drivers/usb/gadget/function/u_serial.h:16,
> from drivers/usb/gadget/legacy/cdc2.c:17:
>>> include/linux/usb/cdc.h:23: error: redefinition of 'struct usb_cdc_parsed_header'
> include/linux/usb/cdc.h:47: warning: 'struct usb_interface' declared inside parameter list
>>> include/linux/usb/cdc.h:47: error: conflicting types for 'cdc_parse_cdc_header'
> include/linux/usb/cdc.h:47: error: previous declaration of 'cdc_parse_cdc_header' was here
This may be a side effect of the initial warning, does this reproduce with
that fixed? Please show me what the warning looks like in that case.
Thanks.
next prev parent reply other threads:[~2015-09-15 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 19:57 [net-next:master 6/12] include/linux/usb/cdc.h:23: error: redefinition of 'struct usb_cdc_parsed_header' kbuild test robot
2015-09-15 20:27 ` David Miller [this message]
2015-09-16 13:06 ` Fengguang Wu
2015-09-16 17:54 ` David Miller
2015-09-16 22:51 ` Fengguang Wu
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=20150915.132742.739418011603329556.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.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;
as well as URLs for NNTP newsgroup(s).