Hi Arjun,
On Sun, 14 Feb 2021 13:40:38 -0800 Arjun Roy wrote:
>
> Sorry, I was confused from the prior email. Is any action required at
> the moment, or not?
No. This is just something that the net-next and bpf-next maintainers
need to sort out when they merge their trees.
--
Cheers,
Stephen
On Sun, Feb 14, 2021 at 1:13 PM Stephen Rothwell wrote:
>
> Hi all,
>
> On Mon, 25 Jan 2021 11:12:23 +1100 Stephen Rothwell
> wrote:
> >
> > Today's linux-next merge of the bpf-next tree got a conflict in:
> >
> > net/ipv4/tcp.c
> >
> > between commit:
> >
> > 7eeba1706eba ("tcp: Add
Hi all,
On Mon, 25 Jan 2021 11:12:23 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> net/ipv4/tcp.c
>
> between commit:
>
> 7eeba1706eba ("tcp: Add receive timestamp support for receive zerocopy.")
>
> from the net-next tree and
On Sun, Jan 24, 2021 at 4:12 PM Stephen Rothwell wrote:
>
> Hi all,
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> net/ipv4/tcp.c
>
> between commit:
>
> 7eeba1706eba ("tcp: Add receive timestamp support for receive zerocopy.")
>
> from the net-next tree and commit:
Thanks, the merge resolution looks good to me!
On Sun, Jan 24, 2021 at 4:12 PM Stephen Rothwell wrote:
>
> Hi all,
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> net/ipv4/tcp.c
>
> between commit:
>
> 7eeba1706eba ("tcp: Add receive timestamp support for receive
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
net/ipv4/tcp.c
between commit:
7eeba1706eba ("tcp: Add receive timestamp support for receive zerocopy.")
from the net-next tree and commit:
9cacf81f8161 ("bpf: Remove extra lock_sock for TCP_ZEROCOPY_RECEIVE")
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
net/core/dev.c
between commit:
829eb208e80d ("rtnetlink: add support for protodown reason")
from the net-next tree and commits:
7f0a838254bd ("bpf, xdp: Maintain info on attached XDP BPF programs in
net_device")
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
include/net/xdp.h
between commit:
2f0bc54ba9a8 ("xdp: introduce xdp_get_shared_info_from_{buff, frame} utility
routines")
from the net-next tree and commits:
9216477449f3 ("bpf: cpumap: Add the possibility to
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
include/linux/filter.h
between commit:
4d295e546115 ("net: simplify cBPF setsockopt compat handling")
from the net-next tree and commits:
e9ddbb7707ff ("bpf: Introduce SK_LOOKUP program type with a dedicated
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlx5/core/en_main.c
between commit:
8960b38932be ("linux/dim: Rename externally used net_dim members")
from the net-next tree and commits:
db05815b36cb ("net/mlx5e: Add XSK zero-copy
On 04/26/2018 02:49 AM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> tools/testing/selftests/bpf/.gitignore
>
> between commit:
>
> 0abf854d7cbb ("selftests: bpf: update .gitignore with missing generated
> files")
>
> from the
On 04/26/2018 02:49 AM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> tools/testing/selftests/bpf/.gitignore
>
> between commit:
>
> 0abf854d7cbb ("selftests: bpf: update .gitignore with missing generated
> files")
>
> from the
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
tools/testing/selftests/bpf/.gitignore
between commit:
0abf854d7cbb ("selftests: bpf: update .gitignore with missing generated
files")
from the net-next tree and commit:
b6fd9cf796e6 ("selftests: bpf: update
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
tools/testing/selftests/bpf/.gitignore
between commit:
0abf854d7cbb ("selftests: bpf: update .gitignore with missing generated
files")
from the net-next tree and commit:
b6fd9cf796e6 ("selftests: bpf: update
14 matches
Mail list logo
