netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Yonghong Song <yhs@fb.com>, bpf@vger.kernel.org, netdev@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>, kernel-team@fb.com
Subject: Re: [PATCH bpf-next v4 0/2] bpf: avoid iterating duplicated files for task_file iterator
Date: Wed, 2 Sep 2020 16:56:27 +0200	[thread overview]
Message-ID: <b14d7e6f-5b55-0132-b9b6-613d5ed138d2@iogearbox.net> (raw)
In-Reply-To: <20200902023112.1672735-1-yhs@fb.com>

On 9/2/20 4:31 AM, Yonghong Song wrote:
[...]
>    v3 -> v4:
>      - avoid using empty string in the CHECK macro. (Andrii)

Applied, thanks!

      parent reply	other threads:[~2020-09-02 14:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02  2:31 [PATCH bpf-next v4 0/2] bpf: avoid iterating duplicated files for task_file iterator Yonghong Song
2020-09-02  2:31 ` [PATCH bpf-next v4 1/2] " Yonghong Song
2020-09-02  2:31 ` [PATCH bpf-next v4 2/2] selftests/bpf: test task_file iterator without visiting pthreads Yonghong Song
2020-09-02 14:56 ` Daniel Borkmann [this message]

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=b14d7e6f-5b55-0132-b9b6-613d5ed138d2@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=kernel-team@fb.com \
    --cc=netdev@vger.kernel.org \
    --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 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).