[PATCH 1/5] samples/bpf: fix test_lru_dist build

Fix the following error by removing a duplicate struct definition: samples/bpf/test_lru_dist.c:39:8: error: redefinition of ‘struct list_head’ 39 | struct list_head { |^ In file included from samples/bpf/test_lru_dist.c:9: ./tools/include/linux/types.h:69:8: note: original

[PATCH 4/5] samples/bpf: fix tracex5_user build error

Add missing symbols to tools/include/linux/filter.h to fix a build failure: make -C samples/bpf/../../tools/lib/bpf/ RM='rm -rf' LDFLAGS= srctree=samples/bpf/../../ O= HOSTCC samples/bpf/tracex5_user.o samples/bpf/tracex5_user.c: In function ‘install_accept_all_seccomp’: samples/bpf/tracex5_us

[PATCH 5/5] samples/bpf: fix hbm build error

Fix the following build error by declaring bpf_spin_lock in hbm.c. Including the UAPI header generates tons of redefined symbol errors, and including it in hbm.h breaks hbm_out_kern.c. make -C samples/bpf/../../tools/lib/bpf/ RM='rm -rf' LDFLAGS= srctree=samples/bpf/../../ O= HOSTCC samples/bp

[PATCH v2] net: phy: rename Asix Electronics PHY driver

Commit 31dd83b96641 ("net-next: phy: new Asix Electronics PHY driver") introduced a new PHY driver drivers/net/phy/asix.c that causes a module name conflict with a pre-existiting driver (drivers/net/usb/asix.c). The PHY driver is used by the X-Surf 100 ethernet card driver, and loaded by that driv

Re: [PATCH 0/3] resolve module name conflict for asix PHY and USB modules

Thanks Andrew, makes perfect sense - patch resent. Cheers, Michael Am 18.05.2019 um 09:20 schrieb Andrew Lunn: On Sat, May 18, 2019 at 08:25:15AM +1200, Michael Schmitz wrote: Haven't heard back in a while, so here goes: Commit 31dd83b96641 ("net-next: phy: new Asix Electronics PHY

Re: [PATCH] net/mlx5e: restrict the real_dev of vlan device is the same as uplink device

There will be multiple vlan device which maybe not belong to the uplink rep device, so wen can limit it 在 2019/5/18 4:30, Saeed Mahameed 写道: > On Wed, 2019-05-15 at 17:25 +0800, we...@ucloud.cn wrote: >> From: wenxu >> >> When register indr block for vlan device, it should check the >> real_dev

Re: [PATCH v2] net/mlx5e: Add bonding device for indr block to offload the packet received from bonding device

在 2019/5/18 6:11, Mark Bloch 写道: > > On 5/17/19 2:17 AM, we...@ucloud.cn wrote: >> From: wenxu >> >> The mlx5e support the lag mode. When add mlx_p0 and mlx_p1 to bond0. >> packet received from mlx_p0 or mlx_p1 and in the ingress tc flower >> forward to vf0. The tc rule can't be offloaded becaus

[PATCH v2] net: Add UNIX_DIAG_UID to Netlink UNIX socket diagnostics.

Author: Felipe Gasper Date: Fri May 17 16:54:40 2019 -0500 net: Add UNIX_DIAG_UID to Netlink UNIX socket diagnostics. This adds the ability for Netlink to report a socket’s UID along with the other UNIX diagnostic information that is already available. This will allow diagnostic to

patch for iproute2

Hello iproute2 maintainer. (Sorry, I don't know your name) I recently noticed a discrepancy: the internal documentation for the ip command says that an *RTT* value can be sufficed with "s" (second) or "ms" (millisecond), but in practice no suffix of any kind is accepted. I found that that comm

Re: [PATCH v2] net/mlx5e: Add bonding device for indr block to offload the packet received from bonding device

On 5/17/2019 20:17, wenxu wrote: > > 在 2019/5/18 6:11, Mark Bloch 写道: >> >> On 5/17/19 2:17 AM, we...@ucloud.cn wrote: >>> From: wenxu >>> >>> The mlx5e support the lag mode. When add mlx_p0 and mlx_p1 to bond0. >>> packet received from mlx_p0 or mlx_p1 and in the ingress tc flower >>> forward

<    1   2