From: Nicolas Schier <nsc@kernel.org>
To: David Disseldorp <ddiss@suse.de>
Cc: Nathan Chancellor <nathan@kernel.org>,
linux-kbuild@vger.kernel.org, linux-fsdevel@vger.kernel.org,
oe-kbuild-all@lists.linux.dev, linux-next@vger.kernel.org
Subject: Re: [PATCH v3 8/8] initramfs_test: add filename padding test case
Date: Thu, 21 Aug 2025 07:40:36 +0200 [thread overview]
Message-ID: <aKaxVPGMRX7ywI5L@levanger> (raw)
In-Reply-To: <20250821150426.40f14b7f.ddiss@suse.de>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
On Thu, Aug 21, 2025 at 03:04:26PM +1000, David Disseldorp wrote:
> On Wed, 20 Aug 2025 23:02:33 +0200, Nicolas Schier wrote:
>
> > > > > 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.
> >
> > With that change:
> >
> > Acked-by: Nicolas Schier <nsc@kernel.org>
>
> Thanks Nicolas!
> Do you have any suggestions regarding how this patchset should proceed -
> would git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git
> kbuild-next be suitable as a pre-merge-window staging area?
yes, Nathan agreed to pick it up for kbuild-next.
Kind regards,
Nicolas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-08-21 5:43 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
2025-08-20 21:02 ` Nicolas Schier
2025-08-21 5:04 ` David Disseldorp
2025-08-21 5:40 ` Nicolas Schier [this message]
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=aKaxVPGMRX7ywI5L@levanger \
--to=nsc@kernel.org \
--cc=ddiss@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nathan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.