From: Daniel Borkmann <daniel@iogearbox.net>
To: bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, alexei.starovoitov@gmail.com,
davem@davemloft.net
Subject: bpf-next is CLOSED
Date: Mon, 30 Mar 2020 23:49:23 +0200 [thread overview]
Message-ID: <419714c2-e170-5aac-efb0-70aef726bc74@iogearbox.net> (raw)
In-Reply-To: <d677c08c-51fa-7bb3-9f0e-a021ae3d9d72@iogearbox.net>
The merge window is open right now, therefore please send bug fixes only
at this point. bpf-next will open back up in roughly 2 weeks after the
merge window is closed. The last bpf-next PR will go out today to David.
Thank you,
Daniel
next prev parent reply other threads:[~2020-03-30 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 13:14 bpf-next is CLOSED Daniel Borkmann
2020-03-30 21:49 ` Daniel Borkmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-03 14:08 Daniel Borkmann
2020-06-01 0:54 Alexei Starovoitov
2019-09-16 9:59 Daniel Borkmann
2019-11-25 1:29 ` Alexei Starovoitov
2019-07-08 15:22 Daniel Borkmann
2019-05-06 10:10 Daniel Borkmann
2019-03-04 9:45 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=419714c2-e170-5aac-efb0-70aef726bc74@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.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).