From: Mike Galbraith <efault@gmx.de>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: kernel (master) build failure w. !CONFIG_NET_RX_BUSY_POLL
Date: Fri, 30 Jun 2017 04:18:17 +0200 [thread overview]
Message-ID: <1498789097.28164.33.camel@gmx.de> (raw)
In-Reply-To: <20170629.153527.1327069677943074079.davem@davemloft.net>
On Thu, 2017-06-29 at 15:35 -0400, David Miller wrote:
> From: Mike Galbraith <efault@gmx.de>
> Date: Wed, 28 Jun 2017 10:01:00 +0200
>
> > Greetings network wizards,
> >
> > The latest RT explicitly disables CONFIG_NET_RX_BUSY_POLL, thus
> > uncovering $subject. Below is what I did about it.
> >
> > -Mike
> >
> > net: Move napi_hash_add/del() inside CONFIG_NET_RX_BUSY_POLL
> >
> > Since 545cd5e5ec54 ("net: Busy polling should ignore sender CPUs"),
> > kernel build fails when CONFIG_NET_RX_BUSY_POLL is disabled. Move
> > napi_hash_add/del() accordingly.
> >
> > Banged-upon-by: Mike Galbraith <efault@gmx.de>
>
> First, this is in no way a standard signoff or ack tag.
It's not intended to be, it's intended to stress that this in not a
submission, it's a local fix for a problem that network folks will
likely fix up differently... but who knows, showing what I did about it
after taking a look could perhaps save a wee bit of labor, so...
Hohum, so much for good intentions. I though I was clearly showing
that separation of the polling business was not as complete as other
changes led me to believe it is intended to be.
> Second, you must provide the complete set of build failure details
> so that anyone just reading your posting can understand and fully
> review your patch without having to go anywhere else for the
> pertinent information.
Here's the naked failure instead.
CC net/core/dev.o
net/core/dev.c: In function ‘napi_hash_add’:
net/core/dev.c:5315:43: error: ‘MIN_NAPI_ID’ undeclared (first use in this function)
if (unlikely(++napi_gen_id < MIN_NAPI_ID))
^
net/core/dev.c:5315:43: note: each undeclared identifier is reported only once for each function it appears in
scripts/Makefile.build:302: recipe for target 'net/core/dev.o' failed
make[1]: *** [net/core/dev.o] Error 1
Makefile:1663: recipe for target 'net/core/dev.o' failed
make: *** [net/core/dev.o] Error 2
-Mike
prev parent reply other threads:[~2017-06-30 2:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 8:01 kernel (master) build failure w. !CONFIG_NET_RX_BUSY_POLL Mike Galbraith
2017-06-29 19:35 ` David Miller
2017-06-30 2:18 ` Mike Galbraith [this message]
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=1498789097.28164.33.camel@gmx.de \
--to=efault@gmx.de \
--cc=davem@davemloft.net \
--cc=linux-rt-users@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.