On Mon, Apr 12, 2021 at 03:04:16PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from include/asm-generic/bug.h:20,
> from arch/x86/include/asm/bug.h:93,
>
Stephen Rothwell wrote:
> net/bridge/netfilter/ebtables.c:1248:33: error: 'struct netns_xt' has no
> member named 'tables'
> 1248 | list_for_each_entry(t, &net->xt.tables[NFPROTO_BRIDGE], list) {
> | ^
> include/linux/list.h:619:20: note: in definition of m
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from include/asm-generic/bug.h:20,
from arch/x86/include/asm/bug.h:93,
from include/linux/bug.h:5,
from include/linux/mmdeb
Hi Brian,
On Wed, Feb 03, 2021 at 07:52:08PM -0800, Brian Vazquez wrote:
> Hi Stephen, thanks for the report. I'm having trouble trying to
> compile for ppc, but I believe this should fix the problem, could you
> test this patch, please? Thanks!
Could you please submit the patch formally to net-n
Hi everyone,
On Thu, Feb 04, 2021 at 20:38, Stephen Rothwell wrote:
> On Wed, 3 Feb 2021 19:52:08 -0800 Brian Vazquez wrote:
>> Hi Stephen, thanks for the report. I'm having trouble trying to
>> compile for ppc, but I believe this should fix the problem, could you
>> test this patch, please? Tha
Hi Brian,
On Wed, 3 Feb 2021 19:52:08 -0800 Brian Vazquez wrote:
>
> Hi Stephen, thanks for the report. I'm having trouble trying to
> compile for ppc, but I believe this should fix the problem, could you
> test this patch, please? Thanks!
That fixed it, thanks (though the patch was badly wrappe
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
ERROR: modpost: "ip6_dst_check" [vmlinux] is a static EXPORT_SYMBOL
ERROR: modpost: "ipv4_dst_check" [vmlinux] is a static EXPORT_SYMBOL
ERROR: modpost: "ipv4_mtu" [vmlinux] is a static E
On Wed, Dec 16, 2020 at 4:08 AM Stephen Rothwell wrote:
>
> Hi Steven,
>
> On Wed, 16 Dec 2020 02:21:26 + Steven French
> wrote:
> >
> > I applied your patch to the tip of my tree (cifs-2.6.git for-next) -
> > hopefully that makes it easier when I sent the PR in a day or two for
> > cifs/smb
Hi Steven,
On Wed, 16 Dec 2020 02:21:26 + Steven French
wrote:
>
> I applied your patch to the tip of my tree (cifs-2.6.git for-next) -
> hopefully that makes it easier when I sent the PR in a day or two for
> cifs/smb3 changes.
I think you have just made your tree fail to build as nla_strs
Hi all,
On Mon, 14 Dec 2020 13:14:38 +1100 Stephen Rothwell
wrote:
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> fs/cifs/cifs_swn.c: In function 'cifs_swn_notify':
> fs/cifs/cifs_swn.c:450:4: error: implicit declaration of function
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
fs/cifs/cifs_swn.c: In function 'cifs_swn_notify':
fs/cifs/cifs_swn.c:450:4: error: implicit declaration of function
'nla_strlcpy'; did you mean 'nla_strscpy'?
[-Werror=implicit-function-de
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
net/core/xdp.c: In function 'xdp_return_frame_bulk':
net/core/xdp.c:417:3: error: too few arguments to function '__xdp_return'
417 | __xdp_return(xdpf->data, &xdpf->mem, false);
On 10/6/20 7:41 AM, Stephen Rothwell wrote:
On Tue, 6 Oct 2020 07:13:01 +0200 Christoph Hellwig wrote:
On Tue, Oct 06, 2020 at 02:58:47PM +1100, Stephen Rothwell wrote:
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
It actually doe
Hi Christoph,
On Tue, 6 Oct 2020 07:13:01 +0200 Christoph Hellwig wrote:
>
> On Tue, Oct 06, 2020 at 02:58:47PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the net-next tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
>
> It actually doesn't need
On Tue, Oct 06, 2020 at 02:58:47PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
It actually doesn't need that or the two other internal headers.
Bjoern has a fixed, and it was supposed to be queued
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
net/xdp/xsk_buff_pool.c:7:10: fatal error: linux/dma-noncoherent.h: No such
file or directory
7 | #include
| ^
Caused by commit
1c1efc2af158 (
Hi Dave,
On Thu, 01 Oct 2020 18:40:13 -0700 (PDT) David Miller
wrote:
>
> From: Stephen Rothwell
> Date: Tue, 29 Sep 2020 13:04:46 +1000
>
> > Caused by commit
> >
> > eff7423365a6 ("net: core: introduce struct netdev_nested_priv for nested
> > interface infrastructure")
> >
> > interacti
From: Stephen Rothwell
Date: Tue, 29 Sep 2020 13:04:46 +1000
> Caused by commit
>
> eff7423365a6 ("net: core: introduce struct netdev_nested_priv for nested
> interface infrastructure")
>
> interacting with commit
>
> e1189d9a5fbe ("net: marvell: prestera: Add Switchdev driver implementat
Hi Vadym,
On Thu, 1 Oct 2020 02:06:05 +0300 Vadym Kochan wrote:
>
> On Thu, Oct 01, 2020 at 08:09:16AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> [CUT]
> >
> > I am still getting this build failure ...
> >
> > --
>
> I just 've checked linux-next/master and it builds fine at least
Hi Stephen,
On Thu, Oct 01, 2020 at 08:09:16AM +1000, Stephen Rothwell wrote:
> Hi all,
>
[CUT]
>
> I am still getting this build failure ...
>
> --
I just 've checked linux-next/master and it builds fine at least with my custom
config, do/how I need to handle this case ?
I see the changes y
Hi all,
On Tue, 29 Sep 2020 13:04:46 +1000 Stephen Rothwell
wrote:
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/net/ethernet/marvell/prestera/prestera_main.c: In function
> 'prestera_port_dev_lower_find':
> drivers/net/ethe
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/net/ethernet/marvell/prestera/prestera_main.c: In function
'prestera_port_dev_lower_find':
drivers/net/ethernet/marvell/prestera/prestera_main.c:504:33: error: passing
argument 2 of
On 2020-08-28 16:42 -0700, Randy Dunlap wrote:
> On 8/28/20 4:16 PM, Brian Vazquez wrote:
>> On Fri, Aug 28, 2020 at 8:12 AM Randy Dunlap wrote:
>>>
>>> On 8/28/20 8:09 AM, Sven Joachim wrote:
On 2020-08-27 11:12 -0700, Brian Vazquez wrote:
> I've been trying to reproduce it with yo
On 8/28/20 4:16 PM, Brian Vazquez wrote:
> On Fri, Aug 28, 2020 at 8:12 AM Randy Dunlap wrote:
>>
>> On 8/28/20 8:09 AM, Sven Joachim wrote:
>>> On 2020-08-27 11:12 -0700, Brian Vazquez wrote:
>>>
I've been trying to reproduce it with your config but I didn't
succeed. I also looked at th
On 8/28/20 8:09 AM, Sven Joachim wrote:
> On 2020-08-27 11:12 -0700, Brian Vazquez wrote:
>
>> I've been trying to reproduce it with your config but I didn't
>> succeed. I also looked at the file after the preprocessor and it
>> looked good:
>>
>> ret = ({ __builtin_expect(!!(ops->match == fib6_ru
On 2020-08-27 11:12 -0700, Brian Vazquez wrote:
> I've been trying to reproduce it with your config but I didn't
> succeed. I also looked at the file after the preprocessor and it
> looked good:
>
> ret = ({ __builtin_expect(!!(ops->match == fib6_rule_match), 1) ?
> fib6_rule_match(rule, fl, flags
On 2020-08-22 08:16 +0200, Sven Joachim wrote:
> On 2020-08-21 09:23 -0700, Brian Vazquez wrote:
>
>> Hi Sven,
>>
>> Sorry for the late reply, did you still see this after:
>> https://patchwork.ozlabs.org/project/netdev/patch/20200803131948.41736-1-yuehaib...@huawei.com/
>> ??
>
> That patch is ap
On 2020-08-21 09:23 -0700, Brian Vazquez wrote:
> Hi Sven,
>
> Sorry for the late reply, did you still see this after:
> https://patchwork.ozlabs.org/project/netdev/patch/20200803131948.41736-1-yuehaib...@huawei.com/
> ??
That patch is apparently already in 5.9-rc1 as commit 80fbbb1672e7, so
yes
On 2020-07-29 21:27 +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (i386 defconfig)
> failed like this:
>
> x86_64-linux-gnu-ld: net/core/fib_rules.o: in function `fib_rules_lookup':
> fib_rules.c:(.text+0x5c6): undefined reference to `fib6_r
On Wed, Aug 05, 2020 at 03:06:27PM +0200, Stefano Brivio wrote:
> On Wed, 5 Aug 2020 22:31:21 +1000
> Stephen Rothwell wrote:
>
> > Hi all,
> >
> > After merging the net-next tree, today's linux-next build (s390 defconfig)
> > failed like this:
> >
> > net/ipv4/ip_tunnel_core.c:335:2: error: im
On Wed, 5 Aug 2020 15:21:44 +0200
Heiko Carstens wrote:
> On Wed, Aug 05, 2020 at 03:06:27PM +0200, Stefano Brivio wrote:
> > On Wed, 5 Aug 2020 22:31:21 +1000
> > Stephen Rothwell wrote:
> >
> > > Hi all,
> > >
> > > After merging the net-next tree, today's linux-next build (s390 defconfig)
Hi all,
After merging the net-next tree, today's linux-next build (s390 defconfig)
failed like this:
net/ipv4/ip_tunnel_core.c:335:2: error: implicit declaration of function
'csum_ipv6_magic' [-Werror=implicit-function-declaration]
Caused by commit
4cb47a8644cc ("tunnels: PMTU discovery supp
On Wed, 5 Aug 2020 22:31:21 +1000
Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (s390 defconfig)
> failed like this:
>
> net/ipv4/ip_tunnel_core.c:335:2: error: implicit declaration of function
> 'csum_ipv6_magic' [-Werror=implicit-function-dec
Hi all,
After merging the net-next tree, today's linux-next build (i386 defconfig)
failed like this:
x86_64-linux-gnu-ld: net/core/fib_rules.o: in function `fib_rules_lookup':
fib_rules.c:(.text+0x5c6): undefined reference to `fib6_rule_match'
x86_64-linux-gnu-ld: fib_rules.c:(.text+0x5d8): undef
On 13/07/2020 04:54, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> net/bridge/br_netlink_tunnel.c: In function '__vlan_tunnel_handle_range':
> net/bridge/br_netlink_tunnel.c:271:26: error: implicit
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
net/bridge/br_netlink_tunnel.c: In function '__vlan_tunnel_handle_range':
net/bridge/br_netlink_tunnel.c:271:26: error: implicit declaration of function
'br_vlan_can_enter_range'; did yo
From: Stephen Rothwell
Date: Mon, 4 Feb 2019 15:34:46 +1100
> From: Stephen Rothwell
> Date: Mon, 4 Feb 2019 15:24:11 +1100
> Subject: [PATCH] socket: fix for Add SO_TIMESTAMP[NS]_NEW
>
> Fixes: 887feae36aee ("socket: Add SO_TIMESTAMP[NS]_NEW")
> Signed-off-by: Stephen Rothwell
Thanks for fix
Hi all,
After merging the net-next tree, today's linux-next build (sparc64
defconfig) failed like this:
/home/sfr/next/next/net/core/sock.c: In function 'sock_setsockopt':
/home/sfr/next/next/net/core/sock.c:1146:2: error: duplicate case value
case SO_BINDTOIFINDEX:
^~~~
/home/sfr/next/next/n
From: Stephen Rothwell
Date: Tue, 29 Jan 2019 16:17:42 +1100
> I have added the following fix patch for today:
>
> From: Stephen Rothwell
> Date: Tue, 29 Jan 2019 16:13:08 +1100
> Subject: [PATCH] enetc: include linux/vmalloc.h for vzalloc etc
>
> Fixes: d4fd0404c1c9 ("enetc: Introduce basic P
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/net/ethernet/freescale/enetc/enetc.c: In function 'enetc_alloc_txbdr':
drivers/net/ethernet/freescale/enetc/enetc.c:685:17: error: implicit
declaration of function 'vzalloc'; did yo
Stephen Rothwell writes:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/net/vxlan.c: In function 'vxlan_changelink':
> drivers/net/vxlan.c:3763:10: error: too few arguments to function
> 'vxlan_fdb_update'
> err =
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/net/vxlan.c: In function 'vxlan_changelink':
drivers/net/vxlan.c:3763:10: error: too few arguments to function
'vxlan_fdb_update'
err = vxlan_fdb_update(vxlan, all_zeros_mac,
Hi,
On Mon, 2018-12-17 at 12:36 +1100, Stephen Rothwell wrote:
> After merging the net-next tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> In file included from net/core/dev.c:148:
> net/core/dev.c: In function 'napi_gro_complete':
> net/core/dev.c:5364:26: error:
Hi all,
After merging the net-next tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from net/core/dev.c:148:
net/core/dev.c: In function 'napi_gro_complete':
net/core/dev.c:5364:26: error: 'inet_gro_complete' undeclared (first use in
this function); did
Hi all,
After merging the net-next tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/ptp/ptp_qoriq.o: In function `qoriq_ptp_probe':
ptp_qoriq.c:(.text+0xd0c): undefined reference to `__aeabi_uldivmod'
Caused by commit
91305f281262 ("ptp_qoriq: support automati
> [Christoph, I noticed that the comment above datagram_poll in
> net/core/datagram.c needs the function name updated]
I'll send a fix for that.
>
> I have added the following merge fix patch for today:
This looks correct, thanks!
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
net/xdp/xsk.c: In function 'xsk_poll':
net/xdp/xsk.c:207:22: error: implicit declaration of function 'datagram_poll';
did you mean 'datagram_poll_mask'? [-Werror=implicit-function-declaratio
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
x86_64-linux-ld: unknown architecture of input file
`net/bpfilter/bpfilter_umh.o' is incompatible with i386:x86-64 output
Caused by commit
d2ba09c17a06 ("net: add skeleton of bpfilter ke
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
net/core/devlink.c: In function 'devlink_resource_validate_size':
net/core/devlink.c:2349:34: error: invalid type argument of '->' (have 'struct
devlink_resource_size_params')
if (size > r
From: Stephen Rothwell
Date: Mon, 29 Jan 2018 12:50:28 +1100
> I have applied the following merge fix patch for today:
>
> From: Stephen Rothwell
> Date: Mon, 29 Jan 2018 12:34:37 +1100
> Subject: [PATCH] net: fixup for "net: tcp: close sock if net namespace is
> exiting"
>
> Signed-off-by: S
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from /home/sfr/next/next/include/linux/init_task.h:17:0,
from /home/sfr/next/next/init/init_task.c:2:
/home/sfr/next/next/include/net/net_namespace.h: In
On Fri, Jan 12, 2018 at 05:21:54PM +0100, Daniel Borkmann wrote:
> On 01/12/2018 04:56 PM, Alexei Starovoitov wrote:
> > On Fri, Jan 12, 2018 at 11:45:42AM +0100, Daniel Borkmann wrote:
> >> On 01/12/2018 05:21 AM, Alexei Starovoitov wrote:
> >>> On Thu, Jan 11, 2018 at 10:11:45PM -0500, David Mill
On 01/12/2018 04:56 PM, Alexei Starovoitov wrote:
> On Fri, Jan 12, 2018 at 11:45:42AM +0100, Daniel Borkmann wrote:
>> On 01/12/2018 05:21 AM, Alexei Starovoitov wrote:
>>> On Thu, Jan 11, 2018 at 10:11:45PM -0500, David Miller wrote:
From: Alexei Starovoitov
Date: Wed, 10 Jan 2018 17:5
On Fri, Jan 12, 2018 at 11:45:42AM +0100, Daniel Borkmann wrote:
> On 01/12/2018 05:21 AM, Alexei Starovoitov wrote:
> > On Thu, Jan 11, 2018 at 10:11:45PM -0500, David Miller wrote:
> >> From: Alexei Starovoitov
> >> Date: Wed, 10 Jan 2018 17:58:54 -0800
> >>
> >>> On Thu, Jan 11, 2018 at 11:53:5
On 01/12/2018 05:21 AM, Alexei Starovoitov wrote:
> On Thu, Jan 11, 2018 at 10:11:45PM -0500, David Miller wrote:
>> From: Alexei Starovoitov
>> Date: Wed, 10 Jan 2018 17:58:54 -0800
>>
>>> On Thu, Jan 11, 2018 at 11:53:55AM +1100, Stephen Rothwell wrote:
Hi all,
After merging the n
On Thu, Jan 11, 2018 at 10:11:45PM -0500, David Miller wrote:
> From: Alexei Starovoitov
> Date: Wed, 10 Jan 2018 17:58:54 -0800
>
> > On Thu, Jan 11, 2018 at 11:53:55AM +1100, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> After merging the net-next tree, today's linux-next build (x86_64
> >> a
From: Alexei Starovoitov
Date: Wed, 10 Jan 2018 17:58:54 -0800
> On Thu, Jan 11, 2018 at 11:53:55AM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> After merging the net-next tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> kernel/bpf/verifier.o: In function `bpf_
On Thu, Jan 11, 2018 at 11:53:55AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> kernel/bpf/verifier.o: In function `bpf_check':
> verifier.c:(.text+0xd86e): undefined reference to `bpf_patch_ca
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
kernel/bpf/verifier.o: In function `bpf_check':
verifier.c:(.text+0xd86e): undefined reference to `bpf_patch_call_args'
Caused by commit
1ea47e01ad6e ("bpf: add support for bpf_call to in
From: Stephen Rothwell
Date: Wed, 10 Jan 2018 15:06:14 +1100
> From: Stephen Rothwell
> Date: Wed, 10 Jan 2018 15:01:41 +1100
> Subject: [PATCH] tuntap: fix for "tuntap: XDP transmission"
>
> Signed-off-by: Stephen Rothwell
Applied, thanks Stephen.
On 2018年01月10日 12:06, Stephen Rothwell wrote:
Hi all,
After merging the net-next tree, today's linux-next build (sparc64
defconfig) failed like this:
net/socket.o: In function `tun_xdp_to_ptr':
(.text+0x3180): multiple definition of `tun_xdp_to_ptr'
fs/compat_ioctl.o:compat_ioctl.c:(.text+0x0
Hi all,
After merging the net-next tree, today's linux-next build (sparc64
defconfig) failed like this:
net/socket.o: In function `tun_xdp_to_ptr':
(.text+0x3180): multiple definition of `tun_xdp_to_ptr'
fs/compat_ioctl.o:compat_ioctl.c:(.text+0x0): first defined here
net/socket.o: In function `t
Hi Stephen,
On Fri, Dec 22, 2017 at 11:45:19AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
[...]
> I have added the following merge fix patch for today (I am guessing
> a bit here):
>
> From
Hi all,
After merging the net-next tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
net/ipv6/route.c: In function 'inet6_rtm_getroute':
net/ipv6/route.c:4324:25: error: 'struct dst_entry' has no member named 'from'
if (fibmatch && rt->dst.from) {
On Thu, 21 Dec 2017 10:43:04 +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/net/netdevsim/bpf.c: In function 'nsim_bpf_setup_tc_block_cb':
> drivers/net/netdevsim/bpf.c:127:7: error: 'TC_
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/net/netdevsim/bpf.c: In function 'nsim_bpf_setup_tc_block_cb':
drivers/net/netdevsim/bpf.c:127:7: error: 'TC_CLSBPF_REPLACE' undeclared (first
use in this function)
case TC_CLSBPF_
Le 09/28/17 à 18:36, Stephen Rothwell a écrit :
> Hi all,
>
> After merging the net-next tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> net/dsa/slave.c: In function 'dsa_slave_create':
> net/dsa/slave.c:1191:18: error: 'struct dsa_slave_priv' has no member named
Hi all,
After merging the net-next tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
net/dsa/slave.c: In function 'dsa_slave_create':
net/dsa/slave.c:1191:18: error: 'struct dsa_slave_priv' has no member named
'phy'
phy_disconnect(p->phy);
^
Caused by
On Thu, 2017-09-21 at 18:37 -0700, David Miller wrote:
> From: Stephen Rothwell
> Date: Fri, 22 Sep 2017 11:03:55 +1000
>
> > After merging the net-next tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> > net/ipv4/fib_frontend.c: In function 'fib_validate_source
From: Stephen Rothwell
Date: Fri, 22 Sep 2017 11:03:55 +1000
> After merging the net-next tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> net/ipv4/fib_frontend.c: In function 'fib_validate_source':
> net/ipv4/fib_frontend.c:411:16: error: 'struct netns_ipv4' has n
Hi all,
After merging the net-next tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
net/ipv4/fib_frontend.c: In function 'fib_validate_source':
net/ipv4/fib_frontend.c:411:16: error: 'struct netns_ipv4' has no member named
'fib_has_custom_local_routes'
if (net->ipv4.f
Hi all,
After merging the net-next tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
arch/arm/boot/dts/rk3228-evb.dtb: ERROR (phandle_references): Reference to
non-existent node or label "phy0"
Caused by commit
db40f15b53e4 ("ARM: dts: rk3228-evb: Enable the integrate
On 07/17/2017 06:09 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> net/core/filter.o: In function `xdp_do_flush_map':
> filter.c:(.text+0x3770): undefined reference to `__dev_map_flush'
> net/cor
Hi all,
After merging the net-next tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
net/core/filter.o: In function `xdp_do_flush_map':
filter.c:(.text+0x3770): undefined reference to `__dev_map_flush'
net/core/filter.o: In function `__bpf_tx_xdp':
filter.c:(.text+0x56dc):
From: Stephen Rothwell
Date: Mon, 22 May 2017 13:43:00 +1000
> Hi Dave,
>
> On Sun, 21 May 2017 23:14:10 -0400 (EDT) David Miller
> wrote:
>>
>> From: Stephen Rothwell
>> Date: Mon, 22 May 2017 11:16:05 +1000
>>
>> > After merging the net-next tree, today's linux-next build (powerpc
>> > ppc
On Sun, May 21, 2017 at 9:16 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> net/socket.c: In function 'put_ts_pktinfo':
> net/socket.c:695:28: error: 'SCM_TIMESTAMPING_PKTINFO' undeclared (first
Hi Dave,
On Sun, 21 May 2017 23:14:10 -0400 (EDT) David Miller
wrote:
>
> From: Stephen Rothwell
> Date: Mon, 22 May 2017 11:16:05 +1000
>
> > After merging the net-next tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > net/socket.c: In function 'put_ts_pk
From: Stephen Rothwell
Date: Mon, 22 May 2017 11:16:05 +1000
> After merging the net-next tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> net/socket.c: In function 'put_ts_pktinfo':
> net/socket.c:695:28: error: 'SCM_TIMESTAMPING_PKTINFO' undeclared (first use
>
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
net/socket.c: In function 'put_ts_pktinfo':
net/socket.c:695:28: error: 'SCM_TIMESTAMPING_PKTINFO' undeclared (first use in
this function)
put_cmsg(msg, SOL_SOCKET, SCM_TIMESTAMPING_PK
Hi all,
On Tue, 10 Jan 2017 10:59:27 +1100 Stephen Rothwell
wrote:
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> net/smc/af_smc.c: In function 'smc_splice_read':
> net/smc/af_smc.c:1258:39: error: passing argument 1 of
> 'smc->clcso
ACK - smc_splice_read() is just a place holder at the moment. Its
implementation for AF_SMC will follow.
Regards, Ursula Braun
On 01/10/2017 12:59 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> n
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
net/smc/af_smc.c: In function 'smc_splice_read':
net/smc/af_smc.c:1258:39: error: passing argument 1 of
'smc->clcsock->ops->splice_read' from incompatible pointer type
[-Werror=incompatible
On Friday 13 May 2016 17:47:17 Andy Gross wrote:
> On 13 May 2016 at 17:19, Bjorn Andersson wrote:
> > On Fri 13 May 14:01 PDT 2016, Arnd Bergmann wrote:
> >
> >> On Tuesday 10 May 2016 11:39:34 Bjorn Andersson wrote:
> > [..]
> >> > I assume we could have the QRTR go through Andy and arm-soc, wit
On 13 May 2016 at 17:19, Bjorn Andersson wrote:
> On Fri 13 May 14:01 PDT 2016, Arnd Bergmann wrote:
>
>> On Tuesday 10 May 2016 11:39:34 Bjorn Andersson wrote:
> [..]
>> > I assume we could have the QRTR go through Andy and arm-soc, with
>> > David's approval and this fix squashed in. But we're r
On Fri 13 May 14:01 PDT 2016, Arnd Bergmann wrote:
> On Tuesday 10 May 2016 11:39:34 Bjorn Andersson wrote:
[..]
> > I assume we could have the QRTR go through Andy and arm-soc, with
> > David's approval and this fix squashed in. But we're running rather late
> > in this cycle, perhaps we should j
On Tuesday 10 May 2016 11:39:34 Bjorn Andersson wrote:
> On Mon 09 May 18:29 PDT 2016, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > After merging the net-next tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > net/qrtr/smd.c:106:14: error: initialization from inc
On Mon 09 May 18:29 PDT 2016, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> net/qrtr/smd.c:106:14: error: initialization from incompatible pointer type
> [-Werror=incompatible-pointer-types]
> .cal
On 9 May 2016 at 20:29, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> net/qrtr/smd.c:106:14: error: initialization from incompatible pointer type
> [-Werror=incompatible-pointer-types]
> .callback =
From: Stephen Rothwell
Date: Tue, 10 May 2016 11:29:14 +1000
> Caused by commit
>
> e800072c18f0 ("Merge
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net")
>
> which seems to have reversed some of the merge fixes in commit
>
> cba653210056 ("Merge
> git://git.kernel.org/pub/scm/
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
net/qrtr/smd.c:106:14: error: initialization from incompatible pointer type
[-Werror=incompatible-pointer-types]
.callback = qcom_smd_qrtr_callback,
^
net/qrtr/smd.c:106:14:
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from drivers/net/ethernet/mellanox/mlx5/core/en_main.c:37:0:
drivers/net/ethernet/mellanox/mlx5/core/en.h:525:29: error: field 'fts' has
incomplete type
struct mlx5e_flow_
On Fri, Apr 22, 2016 at 04:20:43PM -0700, Jeff Kirsher wrote:
> On Fri, 2016-04-22 at 10:20 +0100, Mark Brown wrote:
> > > Jeff, please have your folks look into this. Probably just a
> > simple
> > > conversion to mdelay().
> > This is still present, it's been breaking ARM allmodconfig builds f
On Fri, 2016-04-22 at 10:20 +0100, Mark Brown wrote:
> On Wed, Apr 13, 2016 at 11:15:13AM -0400, David Miller wrote:
> > From: Stephen Rothwell
>
> > > After merging the net-next tree, today's linux-next build (arm
> > > allmodconfig) failed like thisi (this has actually been failing
> for a
> >
On Wed, Apr 13, 2016 at 11:15:13AM -0400, David Miller wrote:
> From: Stephen Rothwell
> > After merging the net-next tree, today's linux-next build (arm
> > allmodconfig) failed like thisi (this has actually been failing for a
> > few days, now):
> > ERROR: "__bad_udelay" [drivers/net/ethernet/
On Wednesday 13 April 2016 11:15:13 David Miller wrote:
> From: Stephen Rothwell
> Date: Wed, 13 Apr 2016 17:50:28 +1000
>
> > After merging the net-next tree, today's linux-next build (arm
> > allmodconfig) failed like thisi (this has actually been failing for a
> > few days, now):
> >
> > ERRO
From: Stephen Rothwell
Date: Wed, 13 Apr 2016 17:50:28 +1000
> After merging the net-next tree, today's linux-next build (arm
> allmodconfig) failed like thisi (this has actually been failing for a
> few days, now):
>
> ERROR: "__bad_udelay" [drivers/net/ethernet/intel/ixgbe/ixgbe.ko] undefined!
Hi all,
[A report from Mark's buildbot]
After merging the net-next tree, today's linux-next build (arm
allmodconfig) failed like thisi (this has actually been failing for a
few days, now):
ERROR: "__bad_udelay" [drivers/net/ethernet/intel/ixgbe/ixgbe.ko] undefined!
Caused by commit
49425dfc7
> > After merging the net-next tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > In file included from drivers/net/ethernet/broadcom/bnx2x/bnx2x.h:56:0,
> > from drivers/net/ethernet/broadcom/bnx2x/bnx2x_dcb.c:30:
> > drivers/net/ethernet/broadc
From: Stephen Rothwell
Date: Thu, 18 Feb 2016 12:28:55 +1100
> After merging the net-next tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> In file included from drivers/net/ethernet/broadcom/bnx2x/bnx2x.h:56:0,
> from drivers/net/ethernet/broadcom
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from drivers/net/ethernet/broadcom/bnx2x/bnx2x.h:56:0,
from drivers/net/ethernet/broadcom/bnx2x/bnx2x_dcb.c:30:
drivers/net/ethernet/broadcom/bnx2x/bnx2x
1 - 100 of 113 matches
Mail list logo
