From: Petr Vorel <pvorel@suse.cz>
To: Dai Shili <daisl.fnst@fujitsu.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 1/3] Add SAFE_ACCESS macro
Date: Wed, 23 Mar 2022 20:33:21 +0100 [thread overview]
Message-ID: <Yjt2ATiNR0EChr1k@pevik> (raw)
In-Reply-To: <1647629747-13405-1-git-send-email-daisl.fnst@fujitsu.com>
Hi Dai, Xu,
merged this one.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-03-23 19:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 17:28 [LTP] [PATCH 1/2] Add SAFE_ACCESS macro Dai Shili
2022-03-14 17:28 ` [LTP] [PATCH 2/2] Make use of SAFE_ACCESS Dai Shili
2022-03-14 6:43 ` xuyang2018.jy
2022-03-17 21:00 ` [LTP] [PATCH v2 1/3] Add SAFE_ACCESS macro Dai Shili
2022-03-17 21:00 ` [LTP] [PATCH v2 2/3] Make use of SAFE_ACCESS Dai Shili
2022-03-18 4:02 ` xuyang2018.jy
2022-03-17 21:00 ` [LTP] [PATCH v2 3/3] syscalls/umount2: Convert to new API and use SAFE_ACCESS Dai Shili
2022-03-18 4:03 ` xuyang2018.jy
2022-03-18 5:11 ` xuyang2018.jy
2022-03-18 18:55 ` [LTP] [PATCH v3 1/3] Add SAFE_ACCESS macro Dai Shili
2022-03-18 18:55 ` [LTP] [PATCH v3 2/3] Make use of SAFE_ACCESS Dai Shili
2022-03-23 19:30 ` Petr Vorel
2022-03-23 19:33 ` Petr Vorel
2022-03-18 18:55 ` [LTP] [PATCH v3 3/3] syscalls/umount2: Convert to new API and use SAFE_ACCESS Dai Shili
2022-03-23 19:36 ` Petr Vorel
2022-03-24 2:23 ` daisl.fnst
2022-03-24 15:35 ` [LTP] [PATCH v4] " Dai Shili
2022-03-24 9:11 ` Petr Vorel
2022-03-25 3:00 ` daisl.fnst
2022-03-25 17:29 ` [LTP] [PATCH v5] " Dai Shili
2022-03-25 8:46 ` Petr Vorel
2022-03-24 1:37 ` [LTP] [PATCH v3 3/3] " xuyang2018.jy
2022-03-23 19:24 ` [LTP] [PATCH v3 1/3] Add SAFE_ACCESS macro Petr Vorel
2022-03-24 2:22 ` daisl.fnst
2022-03-23 19:27 ` Petr Vorel
2022-03-23 19:33 ` Petr Vorel [this message]
2022-03-18 3:56 ` [LTP] [PATCH v2 " xuyang2018.jy
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=Yjt2ATiNR0EChr1k@pevik \
--to=pvorel@suse.cz \
--cc=daisl.fnst@fujitsu.com \
--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 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.