From: Mike Rapoport <rppt@kernel.org>
To: Jordan Richards <jordanrichards@google.com>
Cc: dmatlack@google.com, jasonmiu@google.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, pasha.tatashin@soleen.com,
pratyush@kernel.org, shuah@kernel.org
Subject: Re: [PATCH] selftests/liveupdate: add end to end test infrastructure and scripts
Date: Tue, 3 Feb 2026 20:24:45 +0200 [thread overview]
Message-ID: <aYI9bUEodBEU6Zq3@kernel.org> (raw)
In-Reply-To: <20260202214859.662889-1-jordanrichards@google.com>
On Mon, Feb 02, 2026 at 09:48:59PM +0000, Jordan Richards wrote:
> Hi Mike,
>
> Thanks for the feedback.
>
> >> +int sys_ftruncate(int fd, off_t length)
> >> +{
> >> + return my_syscall2(__NR_ftruncate, fd, length);
> >> +}
> >> +
> >> +int ftruncate(int fd, off_t length)
> >> +{
> >> + return __sysret(sys_ftruncate(fd, length));
> >> +}
> >
> > These should be added to nolibc I suppose.
>
> I notice that nolibc has its own tree. If I patch nolibc/sys.h,
> will those changes make their way there? Or should I avoid modifying
> nolibc/sys.h and keep this local copy for now, to be removed if/when
> ftruncate is added to nolibc?
I think you can make this a set of two patches: the first that adds
ftruncate to nolibc and the second with LUO test.
Then with an Ack from nolibc maintainer both can be merged via Andrew's tree.
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-02-03 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 21:44 Jordan Richards
2026-01-27 17:33 ` Mike Rapoport
2026-01-29 22:51 ` David Matlack
2026-02-02 21:48 ` Jordan Richards
2026-02-03 18:24 ` Mike Rapoport [this message]
2026-02-05 22:11 ` Jordan Richards
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=aYI9bUEodBEU6Zq3@kernel.org \
--to=rppt@kernel.org \
--cc=dmatlack@google.com \
--cc=jasonmiu@google.com \
--cc=jordanrichards@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--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