From: Sandeep Patil <sspatil@android.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 3/5] syscalls/asyncio02: convert to new library.
Date: Sun, 9 Jun 2019 17:27:43 -0700 [thread overview]
Message-ID: <20190610002743.GD212690@google.com> (raw)
In-Reply-To: <20190603143137.GA18922@dell5510>
On Mon, Jun 03, 2019 at 04:31:37PM +0200, Petr Vorel wrote:
> Hi,
>
> > The cleanup looks good, but we should also decide what to do with the
> > test as it is in a wrong place. There is no asyncio syscall in Linux and
> > the test actually looks very similar to the stat01.c test, so maybe it
> > would be best to rename the test to stat02.c after the cleanup. What do
> > you think?
> I'd also move it into stat/stat02.c.
I did this now as part of v2. However, the test is still super trivial and
isn't at all unique. All it is now is "verify stat size" and I think stat01
covers it too.
Anyway, its there in the new series if you still see value in having a
stat02.
- ssp
next prev parent reply other threads:[~2019-06-10 0:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-19 0:38 [LTP] [PATCH 0/5] New library conversion for few system call tests Sandeep Patil
2019-05-19 0:38 ` [LTP] [PATCH 1/5] syscalls/adjtimex01: Convert to new library Sandeep Patil
2019-05-29 10:07 ` Cyril Hrubis
2019-05-19 0:38 ` [LTP] [PATCH 2/5] syscalls/adjtimex02: " Sandeep Patil
2019-05-29 10:12 ` Cyril Hrubis
2019-05-19 0:38 ` [LTP] [PATCH 3/5] syscalls/asyncio02: convert " Sandeep Patil
2019-05-29 11:25 ` Cyril Hrubis
2019-06-03 14:31 ` Petr Vorel
2019-06-10 0:27 ` Sandeep Patil [this message]
2019-05-19 0:38 ` [LTP] [PATCH 4/5] syscalls/bdflush01: delete bdflush test Sandeep Patil
2019-05-19 22:21 ` Sandeep Patil
2019-05-19 23:33 ` [LTP] [PATCH v2] " Sandeep Patil
2019-05-22 14:56 ` Cyril Hrubis
2019-05-19 0:38 ` [LTP] [PATCH 5/5] syscalls/bind01: convert to new library Sandeep Patil
2019-05-29 11:51 ` Cyril Hrubis
2019-05-31 17:19 ` Sandeep Patil
2019-06-10 0:26 ` Sandeep Patil
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=20190610002743.GD212690@google.com \
--to=sspatil@android.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.