From: David Disseldorp <ddiss@suse.de>
To: kernel test robot <lkp@intel.com>
Cc: linux-kbuild@vger.kernel.org, linux-fsdevel@vger.kernel.org,
oe-kbuild-all@lists.linux.dev, linux-next@vger.kernel.org,
nsc@kernel.org
Subject: Re: [PATCH v3 8/8] initramfs_test: add filename padding test case
Date: Wed, 20 Aug 2025 11:13:34 +1000 [thread overview]
Message-ID: <20250820111334.51e91938.ddiss@suse.de> (raw)
In-Reply-To: <202508200304.wF1u78il-lkp@intel.com>
On Wed, 20 Aug 2025 04:16:48 +0800, kernel test robot wrote:
> sparse warnings: (new ones prefixed by >>)
> >> init/initramfs_test.c:415:18: sparse: sparse: Initializer entry defined twice
> init/initramfs_test.c:425:18: sparse: also defined here
...
> 407 struct initramfs_test_cpio c[] = { {
> 408 .magic = "070701",
> 409 .ino = 1,
> 410 .mode = S_IFREG | 0777,
> 411 .uid = 0,
> 412 .gid = 0,
> 413 .nlink = 1,
> 414 .mtime = 1,
> > 415 .filesize = 0,
...
> 425 .filesize = sizeof(fdata),
> 426 } };
Thanks. I can send a v4 patchset to address this, or otherwise happy to
have line 415 removed by a maintainer when merged.
next prev parent reply other threads:[~2025-08-20 1:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 3:05 [PATCH v3 0/8] gen_init_cpio: add copy_file_range / reflink support David Disseldorp
2025-08-19 3:05 ` [PATCH v3 1/8] gen_init_cpio: write to fd instead of stdout stream David Disseldorp
2025-08-19 3:05 ` [PATCH v3 2/8] gen_init_cpio: support -o <output_file> parameter David Disseldorp
2025-08-19 3:05 ` [PATCH v3 3/8] gen_init_cpio: attempt copy_file_range for file data David Disseldorp
2025-08-19 3:05 ` [PATCH v3 4/8] gen_init_cpio: avoid duplicate strlen calls David Disseldorp
2025-08-19 3:05 ` [PATCH v3 5/8] gen_initramfs.sh: use gen_init_cpio -o parameter David Disseldorp
2025-08-19 3:05 ` [PATCH v3 6/8] docs: initramfs: file data alignment via name padding David Disseldorp
2025-08-19 3:05 ` [PATCH v3 7/8] gen_init_cpio: add -a <data_align> as reflink optimization David Disseldorp
2025-08-19 3:05 ` [PATCH v3 8/8] initramfs_test: add filename padding test case David Disseldorp
2025-08-19 20:16 ` kernel test robot
2025-08-20 1:13 ` David Disseldorp [this message]
2025-08-20 21:02 ` Nicolas Schier
2025-08-21 5:04 ` David Disseldorp
2025-08-21 5:40 ` Nicolas Schier
2025-08-21 19:09 ` [PATCH v3 0/8] gen_init_cpio: add copy_file_range / reflink support Nathan Chancellor
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=20250820111334.51e91938.ddiss@suse.de \
--to=ddiss@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nsc@kernel.org \
--cc=oe-kbuild-all@lists.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