From: Martin KaFai Lau <martin.lau@linux.dev>
To: alibuda@linux.alibaba.com
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
pabeni@redhat.com, song@kernel.org, sdf@google.com,
haoluo@google.com, yhs@fb.com, edumazet@google.com,
john.fastabend@gmail.com, kpsingh@kernel.org, jolsa@kernel.org,
mjambigi@linux.ibm.com, wenjia@linux.ibm.com,
wintera@linux.ibm.com, dust.li@linux.alibaba.com,
tonylu@linux.alibaba.com, guwen@linux.alibaba.com,
bpf@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
netdev@vger.kernel.org, sidraya@linux.ibm.com,
jaka@linux.ibm.com, martin.lau@kernel.org, eddyz87@gmail.com,
yonghong.song@linux.dev, clm@meta.com, ihor.solodrai@linux.dev,
bot+bpf-ci@kernel.org
Subject: Re: [PATCH bpf-next v5 3/3] bpf/selftests: add selftest for bpf_smc_hs_ctrl
Date: Mon, 10 Nov 2025 15:28:02 -0800 [thread overview]
Message-ID: <0a7d4d89-6619-4fa7-be97-26f1871d348f@linux.dev> (raw)
In-Reply-To: <85f7a32e705dc34a7e76e4f41727076593fa4ad52ce918549103885c9719821a@mail.kernel.org>
On 11/6/25 8:16 PM, bot+bpf-ci@kernel.org wrote:
>> diff --git a/tools/testing/selftests/bpf/config b/tools/testing/selftests/bpf/config
>> index 70b28c1e6..fcd2f9bf7 100644
>> --- a/tools/testing/selftests/bpf/config
>> +++ b/tools/testing/selftests/bpf/config
>> @@ -123,3 +123,8 @@ CONFIG_XDP_SOCKETS=y
>> CONFIG_XFRM_INTERFACE=y
>> CONFIG_TCP_CONG_DCTCP=y
>> CONFIG_TCP_CONG_BBR=y
>> +CONFIG_INFINIBAND=y
>> +CONFIG_SMC=y
>> +CONFIG_SMC_HS_CTRL_BPF=y
>> +CONFIG_DIBS=y
>> +CONFIG_DIBS_LO=y
> \ No newline at end of file
>
> The config file is missing a newline at the end. While not a functional
> issue, this violates POSIX text file conventions and git warns about it.
I fixed it. The set is applied.
next prev parent reply other threads:[~2025-11-10 23:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 3:56 [PATCH bpf-next v5 0/3] net/smc: Introduce smc_hs_ctrl D. Wythe
2025-11-07 3:56 ` [PATCH bpf-next v5 1/3] bpf: export necessary symbols for modules with struct_ops D. Wythe
2025-11-07 3:56 ` [PATCH bpf-next v5 2/3] net/smc: bpf: Introduce generic hook for handshake flow D. Wythe
2025-12-05 4:16 ` Guenter Roeck
2025-12-16 6:43 ` D. Wythe
2025-11-07 3:56 ` [PATCH bpf-next v5 3/3] bpf/selftests: add selftest for bpf_smc_hs_ctrl D. Wythe
2025-11-07 4:16 ` bot+bpf-ci
2025-11-10 23:28 ` Martin KaFai Lau [this message]
2025-11-10 20:10 ` [PATCH bpf-next v5 0/3] net/smc: Introduce smc_hs_ctrl 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=0a7d4d89-6619-4fa7-be97-26f1871d348f@linux.dev \
--to=martin.lau@linux.dev \
--cc=alibuda@linux.alibaba.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bot+bpf-ci@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clm@meta.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=haoluo@google.com \
--cc=ihor.solodrai@linux.dev \
--cc=jaka@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=martin.lau@kernel.org \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=sidraya@linux.ibm.com \
--cc=song@kernel.org \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@linux.ibm.com \
--cc=yhs@fb.com \
--cc=yonghong.song@linux.dev \
/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