From: patchwork-bot+netdevbpf@kernel.org
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: shuah@kernel.org, Liam.Howlett@oracle.com,
anjali.k.kulkarni@oracle.com, naresh.kamboju@linaro.org,
kuba@kernel.org, davem@davemloft.net,
lkft-triage@lists.linaro.org, netdev@vger.kernel.org,
llvm@lists.linux.dev, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH next 0/3] Connector/proc_filter test fixes
Date: Mon, 31 Jul 2023 21:50:22 +0000 [thread overview]
Message-ID: <169084022235.13504.17826979255292322380.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1690564372.git.skhan@linuxfoundation.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 28 Jul 2023 11:29:25 -0600 you wrote:
> This 3 patch series consists of fixes to proc_filter test
> found during linun-next testing.
>
> The first patch fixes the LKFT reported compile error, second
> one adds .gitignore and the third fixes error paths to skip
> instead of fail (root check, and argument checks)
>
> [...]
Here is the summary with links:
- [next,1/3] selftests:connector: Fix Makefile to include KHDR_INCLUDES
https://git.kernel.org/netdev/net-next/c/165f6890586e
- [next,2/3] selftests:connector: Add .gitignore and poupulate it with test
https://git.kernel.org/netdev/net-next/c/f4dcfa6fa1a8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-07-31 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 17:29 [PATCH next 0/3] Connector/proc_filter test fixes Shuah Khan
2023-07-28 17:29 ` [PATCH next 1/3] selftests:connector: Fix Makefile to include KHDR_INCLUDES Shuah Khan
2023-07-31 21:55 ` Anjali Kulkarni
2023-07-28 17:29 ` [PATCH next 2/3] selftests:connector: Add .gitignore and poupulate it with test Shuah Khan
2023-07-31 21:55 ` Anjali Kulkarni
2023-07-31 21:50 ` patchwork-bot+netdevbpf [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=169084022235.13504.17826979255292322380.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=anjali.k.kulkarni@oracle.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
/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).