netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: vapier.adi@gmail.com
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: bridge netpoll support: mismatch between net core and bridge headers
Date: Thu, 02 Dec 2010 09:51:35 -0800 (PST)	[thread overview]
Message-ID: <20101202.095135.226774598.davem@davemloft.net> (raw)
In-Reply-To: <AANLkTimO79DLyCb5vXQ04keX6Mjwv32wNQLRZcfyPNF2@mail.gmail.com>

From: Mike Frysinger <vapier.adi@gmail.com>
Date: Thu, 2 Dec 2010 03:29:17 -0500

> On Wed, Dec 1, 2010 at 19:33, David Miller wrote:
>> Attached.  Also please provide one of the failing ".config" files,
>> and please test if simply going "make oldconfig" unbreaks things.
>> It may be that randconfig allows configurations that the config
>> system normally does not allow.
> 
> hrm, so your patch does fix things.  the downside is that it might be
> caused by kgdboe (which isnt in mainline yet).  that's the only
> randconfig i can find so far to cause the issue.

If that's the case you just need to check and make sure that kgdboe
handles dependencies properly in it's Kconfig changes.

I suspect that simply adding kgdboe as a new "or" case to the
"def_bool" statement of NETPOLL in driver/net/Kconfig will fix the
problem.

If kgdboe is using "select" to handle these dependencies, that's the
bug.

  reply	other threads:[~2010-12-02 17:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-13 23:26 bridge netpoll support: mismatch between net core and bridge headers Mike Frysinger
2010-12-01 19:42 ` David Miller
2010-12-01 21:53   ` Mike Frysinger
2010-12-02  0:33     ` David Miller
2010-12-02  8:29       ` Mike Frysinger
2010-12-02 17:51         ` David Miller [this message]
2010-12-02 21:57           ` Mike Frysinger

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=20101202.095135.226774598.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=vapier.adi@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).