From: patchwork-bot+netdevbpf@kernel.org
To: Sunday Adelodun <adelodunolaoluwa@yahoo.com>
Cc: kuniyu@google.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
shuah@kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org, david.hunter.linux@gmail.com,
linux-kernel-mentees@lists.linuxfoundation.org,
oe-kbuild-all@lists.linux.dev, lkp@intel.com
Subject: Re: [PATCH net-next] selftests: af_unix: remove unused stdlib.h include
Date: Thu, 27 Nov 2025 11:51:26 +0000 [thread overview]
Message-ID: <176424428626.2543014.2747107697046734578.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251125113648.25903-1-adelodunolaoluwa@yahoo.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 25 Nov 2025 12:36:48 +0100 you wrote:
> The unix_connreset.c test included <stdlib.h>, but no symbol from that
> header is used. This causes a fatal build error under certain
> linux-next configurations where stdlib.h is not available.
>
> Remove the unused include to fix the build.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/r/202511221800.hcgCKvVa-lkp@intel.com/
> Signed-off-by: Sunday Adelodun <adelodunolaoluwa@yahoo.com>
>
> [...]
Here is the summary with links:
- [net-next] selftests: af_unix: remove unused stdlib.h include
https://git.kernel.org/netdev/net-next/c/5c9c1e78de1e
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:[~2025-11-27 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251125113648.25903-1-adelodunolaoluwa.ref@yahoo.com>
2025-11-25 11:36 ` [PATCH net-next] selftests: af_unix: remove unused stdlib.h include Sunday Adelodun
2025-11-27 11:51 ` 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=176424428626.2543014.2747107697046734578.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=adelodunolaoluwa@yahoo.com \
--cc=davem@davemloft.net \
--cc=david.hunter.linux@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--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