linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ulf Magnusson <ulfalizer@gmail.com>,
	Bart Van Assche <bart.vanassche@wdc.com>,
	Felipe Balbi <felipe.balbi@linux.intel.com>,
	Hannes Reinecke <hare@suse.com>
Subject: Re: linux-next: build warning after merge of the kbuild tree
Date: Mon, 11 Dec 2017 09:22:20 +0900	[thread overview]
Message-ID: <CAK7LNAQ=PE2yL8T8AaBqovf54Lo_M7Nq+LpQc9VSKBJUHx67dQ@mail.gmail.com> (raw)
In-Reply-To: <20171211095228.21562f56@canb.auug.org.au>

Hi Stephen,

2017-12-11 7:52 GMT+09:00 Stephen Rothwell <sfr@canb.auug.org.au>:
> Hi Masahiro,
>
> After merging the kbuild tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/usb/gadget/Kconfig:487:warning: choice default symbol 'USB_ETH' is not contained in the choice


I had noticed this before merging it.

I expect somebody will fix drivers/usb/gadget/Kconfig.



> Exposed by commit
>
>   2c37e08464a8 ("kconfig: Warn if choice default is not in choice")
>
> Introduced by commit
>
>   7a9618a22aad ("usb: gadget: allow to enable legacy drivers without USB_ETH")
>
> --
> Cheers,
> Stephen Rothwell






-- 
Best Regards
Masahiro Yamada

  reply	other threads:[~2017-12-11  0:22 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-10 22:52 linux-next: build warning after merge of the kbuild tree Stephen Rothwell
2017-12-11  0:22 ` Masahiro Yamada [this message]
2017-12-11 16:11   ` Bart Van Assche
  -- strict thread matches above, loose matches on Subject: below --
2023-10-03 23:13 Stephen Rothwell
2023-08-28  4:57 Stephen Rothwell
2023-08-28 17:28 ` Nick Desaulniers
2021-08-19 23:28 Stephen Rothwell
2021-08-23  0:25 ` Masahiro Yamada
2020-12-20 22:10 Stephen Rothwell
2020-12-09  9:30 Stephen Rothwell
2020-12-09 13:01 ` Dominique Martinet
2020-12-09 20:56   ` Stephen Rothwell
2020-12-10  6:47     ` Dominique Martinet
2020-12-14 20:44 ` Stephen Rothwell
2016-11-30 23:06 Stephen Rothwell
2016-12-01  2:00 ` Nicholas Piggin
2011-05-02  2:18 Stephen Rothwell
2011-05-02  2:24 ` Dave Jones
2011-05-02  3:45   ` Stephen Rothwell
2011-05-02  4:02     ` Dave Jones
2011-05-02  4:44       ` Stephen Rothwell
2011-05-02  4:24     ` Stephen Rothwell
2011-05-02  4:36       ` Dave Jones
2011-05-02  5:57         ` Stephen Rothwell
2011-05-02  4:53       ` Stephen Rothwell
2011-05-02 11:13         ` Michal Marek
2011-05-02 15:17           ` Valdis.Kletnieks
2011-05-02 15:31             ` Michal Marek
2010-12-23  0:00 Stephen Rothwell
2010-09-30  0:52 Stephen Rothwell
2010-09-30 20:24 ` Michal Marek
2010-09-30  0:50 Stephen Rothwell
2010-09-30 20:25 ` Michal Marek

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='CAK7LNAQ=PE2yL8T8AaBqovf54Lo_M7Nq+LpQc9VSKBJUHx67dQ@mail.gmail.com' \
    --to=yamada.masahiro@socionext.com \
    --cc=bart.vanassche@wdc.com \
    --cc=felipe.balbi@linux.intel.com \
    --cc=hare@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=ulfalizer@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;
as well as URLs for NNTP newsgroup(s).