aboutsummaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2016-01-22 11:43:44 +0100
committerDavid S. Miller <davem@davemloft.net>2016-01-24 22:19:55 -0800
commitfacc432faa59414bd7c60c307ff1645154a66c98 (patch)
treeb2e14a59f14e2f0f5cfacecd74186769c451221e /net
parentpptp: fix illegal memory access caused by multiple bind()s (diff)
downloadlinux-dev-facc432faa59414bd7c60c307ff1645154a66c98.tar.xz
linux-dev-facc432faa59414bd7c60c307ff1645154a66c98.zip
net: simplify napi_synchronize() to avoid warnings
The napi_synchronize() function is defined twice: The definition for SMP builds waits for other CPUs to be done, while the uniprocessor variant just contains a barrier and ignores its argument. In the mvneta driver, this leads to a warning about an unused variable when we lookup the NAPI struct of another CPU and then don't use it: ethernet/marvell/mvneta.c: In function 'mvneta_percpu_notifier': ethernet/marvell/mvneta.c:2910:30: error: unused variable 'other_port' [-Werror=unused-variable] There are no other CPUs on a UP build, so that code never runs, but gcc does not know this. The nicest solution seems to be to turn the napi_synchronize() helper into an inline function for the UP case as well, as that leads gcc to not complain about the argument being unused. Once we do that, we can also combine the two cases into a single function definition and use if(IS_ENABLED()) rather than #ifdef to make it look a bit nicer. The warning first came up in linux-4.4, but I failed to catch it earlier. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Fixes: f86428854480 ("net: mvneta: Statically assign queues to CPUs") Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions