From: lic121 <lic121@chinatelecom.cn>
To: "Björn Töpel" <bjorn.topel@gmail.com>
Cc: Magnus Karlsson <magnus.karlsson@gmail.com>,
bpf <bpf@vger.kernel.org>,
Magnus Karlsson <magnus.karlsson@intel.com>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Network Development <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf] libbpf: unmap rings when umem deleted
Date: Wed, 2 Mar 2022 09:06:03 +0000 [thread overview]
Message-ID: <20220302090603.GA12386@vscode> (raw)
In-Reply-To: <CAJ+HfNiXD_T4qdA7hMep0ncTDnPCNdtV74F8P_oTWb=2ZVoG+Q@mail.gmail.com>
On Wed, Mar 02, 2022 at 09:48:33AM +0100, Björn Töpel wrote:
> On Wed, 2 Mar 2022 at 08:29, Magnus Karlsson <magnus.karlsson@gmail.com> wrote:
> > On Tue, Mar 1, 2022 at 6:57 PM lic121 <lic121@chinatelecom.cn> wrote:
> [...]
> > > Signed-off-by: lic121 <lic121@chinatelecom.cn>
>
> In addition to Magnus' comments; Please use your full name, as
> outlined in Documentation/process/5.Posting.rst.
Thanks for the review Björn.
Magnus, please let me know if you can correct the full name when you
apply the patch? Otherwise I can create a MR in libxdp repo. Thanks
full name: Cheng Li
>
> Cheers!
> Björn
next prev parent reply other threads:[~2022-03-02 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 13:26 [PATCH bpf] libbpf: unmap rings when umem deleted lic121
2022-03-02 7:29 ` Magnus Karlsson
2022-03-02 8:48 ` Björn Töpel
2022-03-02 9:06 ` lic121 [this message]
2022-03-02 9:08 ` Magnus Karlsson
2022-03-08 6:03 ` Andrii Nakryiko
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=20220302090603.GA12386@vscode \
--to=lic121@chinatelecom.cn \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.karlsson@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.