From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, konstantin@linuxfoundation.org,
netdev@vger.kernel.org, bpf@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH bpf-next] bpf: Migrate from patchwork.ozlabs.org to patchwork.kernel.org.
Date: Sun, 11 Oct 2020 13:01:49 -0700 [thread overview]
Message-ID: <20201011200149.66537-1-alexei.starovoitov@gmail.com> (raw)
From: Alexei Starovoitov <ast@kernel.org>
Move the bpf/bpf-next patch processing queue to patchwork.kernel.org.
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
---
Hi All BPF developers,
we've migrated bpf patchwork to kernel.org.
Please monitor the bpf queue at
https://patchwork.kernel.org/project/netdevbpf/list/?delegate=121173
The new home provides:
- automatic marking of patches as 'accepted' as soon as they land in bpf/bpf-next trees.
- automatic email notification when patches are pushed into bpf/bpf-next trees.
- automatic marking as 'superseded' when patch series are respun.
- automatic marking with bpf or netdev delegate based on
[PATCH bpf|bpf-next|net|net-next] subject and via file-based pattern matching.
- Fast UI with low latency for those in US and Europe.
- Patches sent to netdev@vger and/or bpf@vger appear in one place.
Thank you, Konstantin, for making it happen.
The patches will still appear at ozlabs.org until it stops receiving emails.
All bpf patches at ozlabs will be marked as 'not applicable'.
The ozlabs instance is deprecated. It will be used as an archive.
---
Documentation/bpf/bpf_devel_QA.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/bpf/bpf_devel_QA.rst b/Documentation/bpf/bpf_devel_QA.rst
index 75a0dca5f295..5b613d2a5f1a 100644
--- a/Documentation/bpf/bpf_devel_QA.rst
+++ b/Documentation/bpf/bpf_devel_QA.rst
@@ -60,13 +60,13 @@ Q: Where can I find patches currently under discussion for BPF subsystem?
A: All patches that are Cc'ed to netdev are queued for review under netdev
patchwork project:
- http://patchwork.ozlabs.org/project/netdev/list/
+ https://patchwork.kernel.org/project/netdevbpf/list/
Those patches which target BPF, are assigned to a 'bpf' delegate for
further processing from BPF maintainers. The current queue with
patches under review can be found at:
- https://patchwork.ozlabs.org/project/netdev/list/?delegate=77147
+ https://patchwork.kernel.org/project/netdevbpf/list/?delegate=121173
Once the patches have been reviewed by the BPF community as a whole
and approved by the BPF maintainers, their status in patchwork will be
--
2.23.0
next reply other threads:[~2020-10-11 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 20:01 Alexei Starovoitov [this message]
2020-10-11 20:10 ` [PATCH bpf-next] bpf: Migrate from patchwork.ozlabs.org to patchwork.kernel.org patchwork-bot+netdevbpf
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=20201011200149.66537-1-alexei.starovoitov@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--cc=konstantin@linuxfoundation.org \
--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).