From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] setregid: use common user and group names.
Date: Wed, 28 Mar 2018 08:07:00 +0200 [thread overview]
Message-ID: <20180328060700.GA25695@x230> (raw)
In-Reply-To: <20180327172440.GM72541@sspatil-desktop.mtv.corp.google.com>
Hi Sandeep,
...
> > > Also, I wouldn't worry about the test breaking on slightly older Android. The
> > > vast majority of LTS tests are run through VTS, where these tests were disabled[1]
> > > due to the failure anyway. This change will allow us to start running them on
> > > all android devices now onwards ..
> > I thought that there could be preprocesor condition for Android defining different users
> > for it, but if you don't need it I'll merge it.
> Yes, we can probable ifdef it in one place using "#ifdef __ANDROID__" or
> other equivalent, but I don't think its needed here. We want to avoid doing
> that as much as possible. It is fair to say these test will be run with VTS
> "now onwards" anyway ..
Thanks for explanation. I agree, makes sense to avoid it where possible.
> > and just note your related commit in commit
> > message:
> > 8e8648463 ("libcutils: Add "daemon" and "bin" users for testing only")
> I'll resend the patch with this added, thanks for the review.
I'm sorry I've added it myself yesterday and pushed:
1b7cf9474 setregid: use common user and group names.
I'll be more patient next time.
> - ssp
Kind regards,
Petr
next prev parent reply other threads:[~2018-03-28 6:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 20:01 [LTP] [PATCH] setregid: use common user and group names Sandeep Patil
2018-03-26 12:42 ` Petr Vorel
2018-03-26 19:29 ` Sandeep Patil
2018-03-27 9:43 ` Petr Vorel
2018-03-27 17:24 ` Sandeep Patil
2018-03-28 6:07 ` Petr Vorel [this message]
2018-03-28 20:32 ` Sandeep Patil
2018-03-27 12:31 ` Petr Vorel
2018-05-03 13:31 ` Cyril Hrubis
2018-05-03 14:08 ` Petr Vorel
2018-05-03 14:17 ` Cyril Hrubis
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=20180328060700.GA25695@x230 \
--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