From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 0/2] Build fixes
Date: Thu, 25 Apr 2024 17:55:30 +0200 [thread overview]
Message-ID: <20240425155533.295195-1-pvorel@suse.cz> (raw)
changes v2->v3
* Use just long long instead of define _GNU_SOURCE (Jan)
Tested:
https://github.com/pevik/ltp/actions/runs/8835557594
Ideally I'd like to merge tomorrow.
Kind regards,
Petr
Petr Vorel (2):
lapi/fs: Replace loff_t with long long
lapi: getrandom05: Add getrandom() fallback
configure.ac | 1 +
include/lapi/fs.h | 6 +++---
include/lapi/getrandom.h | 15 +++++++++++++--
testcases/kernel/syscalls/getrandom/getrandom05.c | 3 ++-
4 files changed, 19 insertions(+), 6 deletions(-)
--
2.43.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2024-04-25 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 15:55 Petr Vorel [this message]
2024-04-25 15:55 ` [LTP] [PATCH v3 1/2] lapi/fs: Replace loff_t with long long Petr Vorel
2024-04-25 15:55 ` [LTP] [PATCH v3 2/2] lapi: getrandom05: Add getrandom() fallback Petr Vorel
2024-04-25 16:06 ` [LTP] [PATCH v3 0/2] Build fixes Jan Stancek
2024-04-25 21:03 ` Petr Vorel
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=20240425155533.295195-1-pvorel@suse.cz \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).