From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Michal Nazarewicz <m.nazarewicz@samsung•com>
Subject: linux-next: usb tree build warning
Date: Wed, 25 Nov 2009 22:35:08 +1100 [thread overview]
Message-ID: <20091125223508.c0924e2d.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
Hi Greg,
Today's linux-next build (x86_64 allmodconfig) produced this warning:
drivers/usb/gadget/multi.c:30:1: warning: "CONFIG_USB_ETH_RNDIS" redefined
In file included from <command-line>:0:
./include/generated/autoconf.h:185:1: warning: this is the location of the previous definition
Introduced by commit a8e2db2fc35a9c4599181730ef5772376232e881 ("USB: g_multi: Multifunction Composite Gadget added").
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2009-11-25 11:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 11:35 Stephen Rothwell [this message]
2009-11-25 11:59 ` [PATCH] USB: g_multi: Fixed '"CONFIG_USB_ETH_RNDIS" redefined' warning Michal Nazarewicz
2009-11-28 18:34 ` Randy Dunlap
2009-11-30 9:55 ` [PATCH] USB: Added USB_ETH_RNDIS to use instead of CONFIG_USB_ETH_RNDIS Michal Nazarewicz
2009-12-01 6:43 ` Randy Dunlap
2010-01-22 13:48 ` [PATCH] USB: g_config: fix CONFIG_USB_G_MULTI_RNDIS usage Michal Nazarewicz
2010-01-22 14:18 ` [PATCH] USB: g_multi: " Michal Nazarewicz
-- strict thread matches above, loose matches on Subject: below --
2009-11-30 6:01 linux-next: usb tree build warning Stephen Rothwell
2009-12-01 16:23 ` Alan Stern
2009-12-08 0:40 ` Greg KH
2009-12-24 0:01 Stephen Rothwell
2009-12-24 0:51 ` Greg KH
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=20091125223508.c0924e2d.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=m.nazarewicz@samsung$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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