From: Yonghong Song <yhs@fb.com>
To: Dmitry Dolgov <9erthalion6@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Song Liu <songliubraving@fb.com>
Subject: Re: [RFC PATCH bpf-next 1/2] bpf: Add bpf_link iterator
Date: Thu, 28 Apr 2022 14:02:12 -0700 [thread overview]
Message-ID: <346052c5-b8ea-8b2c-5e89-522a7f5c4059@fb.com> (raw)
In-Reply-To: <CA+q6zcXkSBrmnUt3jS+zggqJjUFJQ2J_qUmA4HXtcFmYzYppMg@mail.gmail.com>
On 4/28/22 10:07 AM, Dmitry Dolgov wrote:
> On Thu, Apr 28, 2022, 6:14 PM Yonghong Song <yhs@fb.com
> <mailto:yhs@fb.com>> wrote:
>
> >> diff --git a/kernel/bpf/link_iter.c b/kernel/bpf/link_iter.c
> >> new file mode 100644
> >> index 000000000000..fde41d09f26b
> >> --- /dev/null
> >> +++ b/kernel/bpf/link_iter.c
> >> @@ -0,0 +1,107 @@
> >> +// SPDX-License-Identifier: GPL-2.0-only
> >> +/* Copyright (c) 2020 Facebook */
>
> > Change to your own copyright.
>
> Thanks for reviewing. I have to admit I'm not sure how should it look
> like, is there anything like a guideline/best practices about what to
> put into the copyright line?
You can do
/* Copyright (c) 2022 <Your Company Name> */
or
/* Copyright (c) 2022 <Your Name> */
next prev parent reply other threads:[~2022-04-28 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 18:22 [RFC PATCH bpf-next 0/2] bpf: bpf link iterator Dmitrii Dolgov
2022-04-22 18:22 ` [RFC PATCH bpf-next 1/2] bpf: Add bpf_link iterator Dmitrii Dolgov
2022-04-27 19:03 ` Andrii Nakryiko
2022-04-28 16:14 ` Yonghong Song
[not found] ` <CA+q6zcXkSBrmnUt3jS+zggqJjUFJQ2J_qUmA4HXtcFmYzYppMg@mail.gmail.com>
2022-04-28 21:02 ` Yonghong Song [this message]
2022-04-22 18:22 ` [RFC PATCH bpf-next 2/2] selftests/bpf: Add bpf link iter test Dmitrii Dolgov
2022-04-27 19:03 ` Andrii Nakryiko
2022-04-28 16:42 ` Yonghong Song
2022-04-27 19:04 ` [RFC PATCH bpf-next 0/2] bpf: bpf link iterator 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=346052c5-b8ea-8b2c-5e89-522a7f5c4059@fb.com \
--to=yhs@fb.com \
--cc=9erthalion6@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=songliubraving@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