From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/5] Move preadv()/pwritev() backup definitions to LAPI
Date: Fri, 1 Nov 2024 23:40:46 +0100 [thread overview]
Message-ID: <20241101224046.GA1324664@pevik> (raw)
In-Reply-To: <20241101141111.104803-2-mdoucha@suse.cz>
Hi Martin,
> Merge existing LAPI definitions of preadv2()/pwritev2() to lapi/uio.h
> and add preadv()/pwritev() definitions from test code. Also fix minor
> bugs in return value type and offset handling.
Good catch int => ssize_t.
Obviously correct, merged with second commit.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-11-01 22:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 14:11 [LTP] [PATCH 0/5] Add LVM and NFS tests for file data integrity Martin Doucha
2024-11-01 14:11 ` [LTP] [PATCH 1/5] Move preadv()/pwritev() backup definitions to LAPI Martin Doucha
2024-11-01 22:40 ` Petr Vorel [this message]
2024-11-01 14:11 ` [LTP] [PATCH 2/5] Add safe readv()/writev() functions Martin Doucha
2024-11-01 14:11 ` [LTP] [PATCH 3/5] Add test for file data integrity Martin Doucha
2024-12-04 13:45 ` Cyril Hrubis
2024-12-04 14:39 ` Martin Doucha
2024-11-01 14:11 ` [LTP] [PATCH 4/5] Add support for setting loop device size in shell tests Martin Doucha
2024-11-01 22:45 ` Petr Vorel
2024-11-28 8:19 ` Petr Vorel
2024-11-01 14:11 ` [LTP] [PATCH 5/5] Add test for data integrity over NFS Martin Doucha
2024-11-01 23:32 ` Petr Vorel
2024-11-04 13:05 ` Cyril Hrubis
2024-11-04 13:19 ` Cyril Hrubis
2024-11-04 13:32 ` Cyril Hrubis
2024-11-04 15:59 ` Petr Vorel
2024-11-12 21:23 ` Petr Vorel
2024-11-13 13:44 ` Cyril Hrubis
2024-11-04 14:16 ` Petr Vorel
2024-11-12 12:50 ` Martin Doucha
2024-11-12 21:40 ` Petr Vorel
2024-11-13 14:02 ` Martin Doucha
2024-11-13 14:50 ` Petr Vorel
2024-11-13 13:48 ` Cyril Hrubis
2024-11-28 8:27 ` 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=20241101224046.GA1324664@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/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