From: "Günther Noack" <gnoack3000@gmail.com>
To: Chen Ni <nichen@iscas.ac.cn>
Cc: mic@digikod.net, gnoack@google.com, shuah@kernel.org,
linux-security-module@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/landlock: Remove duplicate include of stdio.h
Date: Wed, 11 Feb 2026 09:27:04 +0100 [thread overview]
Message-ID: <20260211.71676f77cada@gnoack.org> (raw)
In-Reply-To: <20260211062122.2975127-1-nichen@iscas.ac.cn>
On Wed, Feb 11, 2026 at 02:21:22PM +0800, Chen Ni wrote:
> Remove duplicate inclusion of stdio.h in fs_bench.c to clean up
> redundant code.
Thanks, well spotted!
Reviewed-by: Günther Noack <gnoack3000@gmail.com>
next prev parent reply other threads:[~2026-02-11 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 6:21 [PATCH] selftests/landlock: Remove duplicate include of stdio.h Chen Ni
2026-02-11 8:27 ` Günther Noack [this message]
2026-02-11 11:16 ` Mickaël Salaün
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=20260211.71676f77cada@gnoack.org \
--to=gnoack3000@gmail.com \
--cc=gnoack@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=nichen@iscas.ac.cn \
--cc=shuah@kernel.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