From: Martin KaFai Lau <martin.lau@linux.dev>
To: Ji Rongfeng <SikoJobs@outlook.com>
Cc: daniel@iogearbox.net, john.fastabend@gmail.com, ast@kernel.org,
andrii@kernel.org, song@kernel.org, yhs@fb.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, bpf@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2] bpf: Upgrade bpf_{g,s}etsockopt return values
Date: Tue, 6 Dec 2022 10:37:42 -0800 [thread overview]
Message-ID: <2118324c-a6e6-775d-77c2-75587e69e7ff@linux.dev> (raw)
In-Reply-To: <DU0P192MB154719A31758750149418C73D61B9@DU0P192MB1547.EURP192.PROD.OUTLOOK.COM>
On 12/6/22 8:35 AM, Ji Rongfeng wrote:
> I have noticed that this patch has been marked as "Changes Requested" for a few
> days, but there's no comment so far, which is abnormal and confusing.
It is obvious that a test is needed for this change.
next prev parent reply other threads:[~2022-12-06 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 17:39 [PATCH bpf-next v2] bpf: Upgrade bpf_{g,s}etsockopt return values Ji Rongfeng
2022-12-06 16:35 ` Ji Rongfeng
2022-12-06 18:37 ` Martin KaFai Lau [this message]
2022-12-07 11:47 ` Ji Rongfeng
2022-12-06 18:36 ` Martin KaFai Lau
2022-12-07 11:19 ` Ji Rongfeng
2022-12-07 21:08 ` Martin KaFai Lau
[not found] ` <7901fd2a-e6d5-8176-73bd-b910f8abee33@outlook.com>
2022-12-07 15:28 ` Ji Rongfeng
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=2118324c-a6e6-775d-77c2-75587e69e7ff@linux.dev \
--to=martin.lau@linux.dev \
--cc=SikoJobs@outlook.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=song@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 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.