Re: linux-next: build warning after merge of the net-next tree

Hi all, On Thu, 25 Mar 2021 17:23:50 +1100 Stephen Rothwell wrote: > > After merging the net-next tree, today's linux-next build (htmldocs) > produced this warning: > > Sphinx parallel build error: > docutils.utils.SystemMessage: >

Re: linux-next: build warning after merge of the net-next tree

Hi Stephen, On Wed, Mar 17, 2021 at 06:56:05PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the net-next tree, today's linux-next build (sparc64 > defconfig) produced this warning: > > drivers/net/ethernet/intel/e1000e/netdev.c:6926:12: warning: > 'e1000e_pm_prepare' defined but

Re: linux-next: build warning after merge of the net-next tree

On Tue, Dec 15, 2020 at 07:01:25AM +1100, Stephen Rothwell wrote: > Hi all, > > On Thu, 26 Nov 2020 17:40:57 +1100 Stephen Rothwell > wrote: > > > > After merging the net-next tree, today's linux-next build (htmldocs) > > produced this warning: > > > > include/linux/phy.h:869: warning:

Re: linux-next: build warning after merge of the net-next tree

Hi all, On Thu, 26 Nov 2020 17:40:57 +1100 Stephen Rothwell wrote: > > After merging the net-next tree, today's linux-next build (htmldocs) > produced this warning: > > include/linux/phy.h:869: warning: Function parameter or member 'config_intr' > not described in 'phy_driver' > > Introduced

Re: linux-next: build warning after merge of the net-next tree

On Tue, Nov 17, 2020 at 9:20 PM Stephen Rothwell wrote: > > After merging the net-next tree, today's linux-next build (htmldocs) > produced this warning: > > Documentation/networking/index.rst:6: WARNING: toctree contains reference to > nonexisting document 'networking/framerelay' > > Introduced

Re: linux-next: build warning after merge of the net-next tree

On Tue, 8 Sep 2020 13:00:00 +1000 Stephen Rothwell wrote: > Hi all, > > After merging the net-next tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > net/bridge/br_multicast.c: In function 'br_multicast_find_port': > net/bridge/br_multicast.c:1818:21: warning:

Re: linux-next: build warning after merge of the net-next tree

On Tue, Jul 7, 2020 at 12:36 PM Stephen Rothwell wrote: > > Hi all, > > After merging the net-next tree, today's linux-next build (sparc64 > defconfig) produced this warning: > > drivers/net/ethernet/sun/niu.c:9903:12: warning: 'niu_resume' defined but not > used [-Wunused-function] > static

RE: linux-next: build warning after merge of the net-next tree

gt; Subject: Re: linux-next: build warning after merge of the net-next tree > > Hi all, > > On Wed, 27 May 2020 01:15:09 + "Kirsher, Jeffrey T" > wrote: > > > > > -Original Message- > > > From: Stephen Rothwell > > > Sent: Monda

Re: linux-next: build warning after merge of the net-next tree

Hi all, On Wed, 27 May 2020 01:15:09 + "Kirsher, Jeffrey T" wrote: > > > -Original Message- > > From: Stephen Rothwell > > Sent: Monday, May 25, 2020 05:40 > > To: David Miller ; Networking > > > > Cc: Linux Next Mailing List ; Linux Kernel > > Mailing > > List ; Lifshits, Vitaly

Re: linux-next: build warning after merge of the net-next tree

Hi all, On Tue, 2 Jun 2020 12:17:35 +1000 Stephen Rothwell wrote: > > Hi all, > > After merging the net-next tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > drivers/net/ethernet/chelsio/cxgb4/cxgb4_uld.c:666:13: warning: > 'cxgb4_uld_in_use' defined but

RE: linux-next: build warning after merge of the net-next tree

> -Original Message- > From: Stephen Rothwell > Sent: Monday, May 25, 2020 05:40 > To: David Miller ; Networking > > Cc: Linux Next Mailing List ; Linux Kernel Mailing > List ; Lifshits, Vitaly > ; > Kirsher, Jeffrey T > Subject: linux-next: build warning after merge of the net-next

Re: linux-next: build warning after merge of the net-next tree

Stephen Rothwell wrote: > diff --git a/net/rxrpc/peer_object.c b/net/rxrpc/peer_object.c > index a7f1a2cdd198..452163eadb98 100644 > --- a/net/rxrpc/peer_object.c > +++ b/net/rxrpc/peer_object.c > @@ -231,7 +231,7 @@ struct rxrpc_peer *rxrpc_alloc_peer(struct rxrpc_local > *local, gfp_t gfp) >

Re: linux-next: build warning after merge of the net-next tree

On 2/21/19 5:06 PM, Stephen Rothwell wrote: > Hi all, > > After merging the net-next tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > drivers/net/ethernet/rocker/rocker_main.c: In function 'rocker_port_attr_set': >

Re: linux-next: build warning after merge of the net-next tree

Le 2/12/19 à 4:51 PM, Stephen Rothwell a écrit : > Hi all, > > After merging the net-next tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > drivers/staging/fsl-dpaa2/ethsw/ethsw.c: In function 'swdev_port_attr_get': >

Re: linux-next: build warning after merge of the net-next tree

Le 2/12/19 à 4:49 PM, Stephen Rothwell a écrit : > Hi all, > > After merging the net-next tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > drivers/net/ethernet/mellanox/mlxsw/spectrum_switchdev.c: In function > 'mlxsw_sp_port_attr_get': >

Re: linux-next: build warning after merge of the net-next tree

Hi Dave, On Sun, 03 Feb 2019 20:26:06 -0800 (PST) David Miller wrote: > > Thanks, I just pushed the following: > > > [PATCH] net: Fix fall through warning in y2038 tstamp changes. > > net/core/sock.c: In function 'sock_setsockopt': > net/core/sock.c:914:3: warning: this

Re: linux-next: build warning after merge of the net-next tree

From: Stephen Rothwell Date: Mon, 4 Feb 2019 10:44:27 +1100 > After merging the net-next tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > net/core/sock.c: In function 'sock_setsockopt': > net/core/sock.c:914:3: warning: this statement may fall through >

Re: linux-next: build warning after merge of the net-next tree

Hi Gustavo, On Tue, 18 Dec 2018 21:07:06 -0600 "Gustavo A. R. Silva" wrote: > > On 12/18/18 8:42 PM, Stephen Rothwell wrote: > > Hi all, > > > > On Thu, 29 Nov 2018 11:24:28 +1100 Stephen Rothwell > > wrote: > >> > >> After merging the net-next tree, today's linux-next build > >>

Re: linux-next: build warning after merge of the net-next tree

Hi Stephen, On 12/18/18 8:42 PM, Stephen Rothwell wrote: Hi all, On Thu, 29 Nov 2018 11:24:28 +1100 Stephen Rothwell wrote: After merging the net-next tree, today's linux-next build (x86_64_allmodconfig) produced this warning: drivers/net/ethernet/freescale/dpaa2/dpaa2-eth.c: In function

Re: linux-next: build warning after merge of the net-next tree

Hi all, On Thu, 29 Nov 2018 11:24:28 +1100 Stephen Rothwell wrote: > > After merging the net-next tree, today's linux-next build > (x86_64_allmodconfig) produced this warning: > > drivers/net/ethernet/freescale/dpaa2/dpaa2-eth.c: In function 'run_xdp': >

Re: linux-next: build warning after merge of the net-next tree

On Fri, Jul 20, 2018 at 08:19:34AM +0900, Masahiro Yamada wrote: > 2018-07-20 7:35 GMT+09:00 Guenter Roeck : > > On Fri, Jul 20, 2018 at 08:09:06AM +1000, Stephen Rothwell wrote: > >> Hi Guenter, > >> > >> On Thu, 19 Jul 2018 06:49:01 -0700 Guenter Roeck > >> wrote: > >> > > >> > On 07/18/2018

Re: linux-next: build warning after merge of the net-next tree

On Fri, Jul 20, 2018 at 08:19:34AM +0900, Masahiro Yamada wrote: > 2018-07-20 7:35 GMT+09:00 Guenter Roeck : > > On Fri, Jul 20, 2018 at 08:09:06AM +1000, Stephen Rothwell wrote: > >> Hi Guenter, > >> > >> On Thu, 19 Jul 2018 06:49:01 -0700 Guenter Roeck > >> wrote: > >> > > >> > On 07/18/2018

Re: linux-next: build warning after merge of the net-next tree

On 03/13/2018 10:33 AM, David Miller wrote: From: "Gustavo A. R. Silva" Date: Tue, 13 Mar 2018 06:46:24 -0500 Hi Stephen, On 03/13/2018 01:11 AM, Stephen Rothwell wrote: Hi all, After merging the net-next tree, today's linux-next build (sparc defconfig) produced

Re: linux-next: build warning after merge of the net-next tree

On 03/13/2018 10:33 AM, David Miller wrote: From: "Gustavo A. R. Silva" Date: Tue, 13 Mar 2018 06:46:24 -0500 Hi Stephen, On 03/13/2018 01:11 AM, Stephen Rothwell wrote: Hi all, After merging the net-next tree, today's linux-next build (sparc defconfig) produced this warning:

Re: linux-next: build warning after merge of the net-next tree

From: "Gustavo A. R. Silva" Date: Tue, 13 Mar 2018 06:46:24 -0500 > Hi Stephen, > > On 03/13/2018 01:11 AM, Stephen Rothwell wrote: >> Hi all, >> After merging the net-next tree, today's linux-next build (sparc >> defconfig) produced this warning: >> net/core/pktgen.c:

Re: linux-next: build warning after merge of the net-next tree

From: "Gustavo A. R. Silva" Date: Tue, 13 Mar 2018 06:46:24 -0500 > Hi Stephen, > > On 03/13/2018 01:11 AM, Stephen Rothwell wrote: >> Hi all, >> After merging the net-next tree, today's linux-next build (sparc >> defconfig) produced this warning: >> net/core/pktgen.c: In function

Re: linux-next: build warning after merge of the net-next tree

Hi Stephen, On 03/13/2018 01:11 AM, Stephen Rothwell wrote: Hi all, After merging the net-next tree, today's linux-next build (sparc defconfig) produced this warning: net/core/pktgen.c: In function 'pktgen_if_write': net/core/pktgen.c:1710:1: warning: the frame size of 1048 bytes is larger

Re: linux-next: build warning after merge of the net-next tree

Hi Stephen, On 03/13/2018 01:11 AM, Stephen Rothwell wrote: Hi all, After merging the net-next tree, today's linux-next build (sparc defconfig) produced this warning: net/core/pktgen.c: In function 'pktgen_if_write': net/core/pktgen.c:1710:1: warning: the frame size of 1048 bytes is larger

Re: linux-next: build warning after merge of the net-next tree

From: Stephen Rothwell Date: Mon, 4 Dec 2017 11:02:49 +1100 > After merging the net-next tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > drivers/net/phy/broadcom.c:391:12: warning: 'bcm5482_read_status' defined but > not used

Re: linux-next: build warning after merge of the net-next tree

From: Stephen Rothwell Date: Mon, 4 Dec 2017 11:02:49 +1100 > After merging the net-next tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > drivers/net/phy/broadcom.c:391:12: warning: 'bcm5482_read_status' defined but > not used [-Wunused-function] > static

Re: linux-next: build warning after merge of the net-next tree

Am 04.12.2017 um 01:02 schrieb Stephen Rothwell: > Hi all, > > After merging the net-next tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > drivers/net/phy/broadcom.c:391:12: warning: 'bcm5482_read_status' defined but > not used [-Wunused-function] > static

Re: linux-next: build warning after merge of the net-next tree

Am 04.12.2017 um 01:02 schrieb Stephen Rothwell: > Hi all, > > After merging the net-next tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > drivers/net/phy/broadcom.c:391:12: warning: 'bcm5482_read_status' defined but > not used [-Wunused-function] > static

Re: linux-next: build warning after merge of the net-next tree

On Wed, Nov 16, 2016 at 11:36:47AM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the net-next tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > kernel/bpf/bpf_lru_list.c: In function > '__bpf_lru_list_rotate_inactive.isra.3': >

Re: linux-next: build warning after merge of the net-next tree

On Wed, Nov 16, 2016 at 11:36:47AM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the net-next tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > kernel/bpf/bpf_lru_list.c: In function > '__bpf_lru_list_rotate_inactive.isra.3': >

Re: linux-next: build warning after merge of the net-next tree

On Tue, Jul 26, 2016 at 11:35 PM, Stephen Rothwell wrote: > Hi David, > > On Tue, 26 Jul 2016 23:19:59 -0700 (PDT) David Miller > wrote: >> >> Fixed thusly: >> >> >> From 36232012344b8db67052432742deaf17f82e70e6 Mon Sep 17

Re: linux-next: build warning after merge of the net-next tree

On Tue, Jul 26, 2016 at 11:35 PM, Stephen Rothwell wrote: > Hi David, > > On Tue, 26 Jul 2016 23:19:59 -0700 (PDT) David Miller > wrote: >> >> Fixed thusly: >> >> >> From 36232012344b8db67052432742deaf17f82e70e6 Mon Sep 17 00:00:00 2001 >> From: "David S. Miller" >> Date:

Re: linux-next: build warning after merge of the net-next tree

Hi David, On Tue, 26 Jul 2016 23:19:59 -0700 (PDT) David Miller wrote: > > Fixed thusly: > > > From 36232012344b8db67052432742deaf17f82e70e6 Mon Sep 17 00:00:00 2001 > From: "David S. Miller" > Date: Tue, 26 Jul 2016 23:19:29

Re: linux-next: build warning after merge of the net-next tree

Hi David, On Tue, 26 Jul 2016 23:19:59 -0700 (PDT) David Miller wrote: > > Fixed thusly: > > > From 36232012344b8db67052432742deaf17f82e70e6 Mon Sep 17 00:00:00 2001 > From: "David S. Miller" > Date: Tue, 26 Jul 2016 23:19:29 -0700 > Subject: [PATCH] xgene: Fix build

Re: linux-next: build warning after merge of the net-next tree

From: Stephen Rothwell Date: Wed, 27 Jul 2016 16:15:33 +1000 > Hi all, > > After merging the net-next tree, today's linux-next build (powerpc > allyesconfig) produced this warning: > > drivers/net/ethernet/apm/xgene/xgene_enet_hw.c: In function >

Re: linux-next: build warning after merge of the net-next tree

From: Stephen Rothwell Date: Wed, 27 Jul 2016 16:15:33 +1000 > Hi all, > > After merging the net-next tree, today's linux-next build (powerpc > allyesconfig) produced this warning: > > drivers/net/ethernet/apm/xgene/xgene_enet_hw.c: In function > 'xgene_enet_phy_connect': >

Re: linux-next: build warning after merge of the net-next tree

On Mon, Jul 11, 2016 at 04:13:11PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the net-next tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning (CONFIG_MPLS is disabled): > > net/ipv4/tunnel4.c: In function 'tunnel4_init': > net/ipv4/tunnel4.c:223:1:

Re: linux-next: build warning after merge of the net-next tree

On Mon, Jul 11, 2016 at 04:13:11PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the net-next tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning (CONFIG_MPLS is disabled): > > net/ipv4/tunnel4.c: In function 'tunnel4_init': > net/ipv4/tunnel4.c:223:1:

Re: linux-next: build warning after merge of the net-next tree

On 2016年07月04日 11:15, Stephen Rothwell wrote: Hi all, After merging the net-next tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: drivers/net/tun.c: In function 'tun_do_read.part.5': /home/sfr/next/next/drivers/net/tun.c:1491:6: warning: 'err' may be used

Re: linux-next: build warning after merge of the net-next tree

On 2016年07月04日 11:15, Stephen Rothwell wrote: Hi all, After merging the net-next tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: drivers/net/tun.c: In function 'tun_do_read.part.5': /home/sfr/next/next/drivers/net/tun.c:1491:6: warning: 'err' may be used

Re: linux-next: build warning after merge of the net-next tree

On 02/15/2016 04:09 AM, Stephen Rothwell wrote: > Hi all, > > After merging the net-next tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > net/ipv4/igmp.c: In function 'igmp_group_added': > net/ipv4/igmp.c:1227:14: warning: unused variable 'net'

Re: linux-next: build warning after merge of the net-next tree

On 02/15/2016 04:09 AM, Stephen Rothwell wrote: > Hi all, > > After merging the net-next tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > net/ipv4/igmp.c: In function 'igmp_group_added': > net/ipv4/igmp.c:1227:14: warning: unused variable 'net'

Re: linux-next: build warning after merge of the net-next tree

On Thu, May 15, 2014 at 10:43 AM, David Miller wrote: > > I've just pushed out a fix for this, thanks everyone. Thanks, David! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at

Re: linux-next: build warning after merge of the net-next tree

From: Cong Wang Date: Thu, 15 May 2014 10:39:20 -0700 > On Wed, May 14, 2014 at 11:47 PM, Stephen Rothwell > wrote: >> Hi all, >> >> After merging the net-next tree, today's linux-next build (powerpc >> allnoconfig) produced this warning: >> >> >> include/net/ip.h:211:5: warning:

Re: linux-next: build warning after merge of the net-next tree

On Wed, May 14, 2014 at 11:47 PM, Stephen Rothwell wrote: > Hi all, > > After merging the net-next tree, today's linux-next build (powerpc > allnoconfig) produced this warning: > > > include/net/ip.h:211:5: warning: "CONFIG_SYSCTL" is not defined [-Wundef] > #if CONFIG_SYSCTL > ^ > >

Re: linux-next: build warning after merge of the net-next tree

On Wed, May 14, 2014 at 11:47 PM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, After merging the net-next tree, today's linux-next build (powerpc allnoconfig) produced this warning: include/net/ip.h:211:5: warning: CONFIG_SYSCTL is not defined [-Wundef] #if CONFIG_SYSCTL ^

Re: linux-next: build warning after merge of the net-next tree

From: Cong Wang xiyou.wangc...@gmail.com Date: Thu, 15 May 2014 10:39:20 -0700 On Wed, May 14, 2014 at 11:47 PM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, After merging the net-next tree, today's linux-next build (powerpc allnoconfig) produced this warning:

Re: linux-next: build warning after merge of the net-next tree

On Thu, May 15, 2014 at 10:43 AM, David Miller da...@davemloft.net wrote: I've just pushed out a fix for this, thanks everyone. Thanks, David! -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at

Re: linux-next: build warning after merge of the net-next tree

From: Stephen Rothwell Date: Wed, 21 Aug 2013 19:10:41 +1000 > Hi all, > > After merging the net-next tree, today's linux-next build (i386 defconfig > and probably others) produced this warning: > > net/ipv6/addrconf.c: In function 'addrconf_notify': > net/ipv6/addrconf.c:2793:22: warning:

Re: linux-next: build warning after merge of the net-next tree

From: Stephen Rothwell s...@canb.auug.org.au Date: Wed, 21 Aug 2013 19:10:41 +1000 Hi all, After merging the net-next tree, today's linux-next build (i386 defconfig and probably others) produced this warning: net/ipv6/addrconf.c: In function 'addrconf_notify':