From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Luca Boccassi <bluca@debian.org>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Networking <netdev@vger.kernel.org>
Subject: Re: linux-next: manual merge of the bpf-next tree with the net tree
Date: Wed, 27 Mar 2019 18:53:30 -0700 [thread overview]
Message-ID: <CAADnVQLoTT3HWbye5=6JjiidFWhorXS=J0ogwj-jEEs9_3mC-w@mail.gmail.com> (raw)
In-Reply-To: <20190327151503.5pdaqiwb7ugm3ly4@ast-mbp>
On Wed, Mar 27, 2019 at 8:15 AM Alexei Starovoitov
<alexei.starovoitov@gmail.com> wrote:
> then get propagated into net-next and then bpf-next will get them as well.
Now it's done.
Luca,
could you please rebase on bpf-next and resubmit your patch?
next prev parent reply other threads:[~2019-03-28 1:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 22:14 linux-next: manual merge of the bpf-next tree with the net tree Stephen Rothwell
2019-03-27 1:56 ` Alexei Starovoitov
2019-03-27 9:26 ` Luca Boccassi
2019-03-27 15:15 ` Alexei Starovoitov
2019-03-28 1:53 ` Alexei Starovoitov [this message]
2019-03-28 11:37 ` Luca Boccassi
-- strict thread matches above, loose matches on Subject: below --
2019-10-13 23:32 Stephen Rothwell
2019-10-15 23:30 ` Stephen Rothwell
2019-12-19 23:23 Stephen Rothwell
2020-07-22 3:21 Stephen Rothwell
2020-07-22 12:17 ` Jakub Sitnicki
2020-07-22 14:42 ` Kuniyuki Iwashima
2020-07-22 15:02 ` Jakub Sitnicki
2020-07-22 15:05 ` Willem de Bruijn
2020-07-22 15:25 ` Jakub Sitnicki
2020-07-22 15:49 ` Willem de Bruijn
2020-07-22 17:14 ` Alexei Starovoitov
2020-07-23 2:11 ` Stephen Rothwell
2022-08-25 1:00 Stephen Rothwell
2022-09-01 1:11 Stephen Rothwell
2022-11-15 23:10 Stephen Rothwell
2024-03-28 1:55 Stephen Rothwell
2024-03-28 1:57 ` Alexei Starovoitov
2024-04-29 1:49 Stephen Rothwell
2024-04-29 18:56 ` Jakub Kicinski
2024-04-29 21:17 ` Daniel Borkmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAADnVQLoTT3HWbye5=6JjiidFWhorXS=J0ogwj-jEEs9_3mC-w@mail.gmail.com' \
--to=alexei.starovoitov@gmail.com \
--cc=bluca@debian.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).