From: Petr Vorel <pvorel@suse.cz>
To: Avinesh Kumar <akumar@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] setegid01.c: Rewrite using new LTP API
Date: Tue, 23 Aug 2022 10:53:30 +0200 [thread overview]
Message-ID: <YwSVit9nNFb1QeRT@pevik> (raw)
In-Reply-To: <20220823074746.28250-1-akumar@suse.de>
Hi Avinesh,
thanks merged, with few small change:
* add the last check of result of SAFE_SETEGID(orig_egid) (was in the original):
SAFE_GETRESGID(&cur_rgid, &cur_egid, &orig_sgid);
TST_EXP_EQ_LU(orig_egid, cur_egid);
I also reword doc and TINFO messages a bit.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-08-23 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 7:47 [LTP] [PATCH] setegid01.c: Rewrite using new LTP API Avinesh Kumar
2022-08-23 8:53 ` Petr Vorel [this message]
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=YwSVit9nNFb1QeRT@pevik \
--to=pvorel@suse.cz \
--cc=akumar@suse.de \
--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