From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/2] syscall/write02.c: Cleanup && convert to new API.
Date: Fri, 26 May 2017 16:16:55 +0200 [thread overview]
Message-ID: <20170526141655.GE6492@rei.lan> (raw)
In-Reply-To: <1492771707-7554-1-git-send-email-huangjh.jy@cn.fujitsu.com>
Hi!
The write01 seems to do pretty much the same but only with a buffer
sized 1 byte. Can you rather add a few lines of code to the write01.c
test so that it tries with different buffer sizes and remove write02.c?
It does not make much sense to keep two tests that does basically the
same.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-05-26 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 10:48 [LTP] [PATCH 1/2] syscall/write02.c: Cleanup && convert to new API Jinhui Huang
2017-04-21 10:48 ` [LTP] [PATCH 2/2] syscall/write03.c: " Jinhui Huang
2017-05-26 14:14 ` Cyril Hrubis
2017-05-26 14:16 ` Cyril Hrubis [this message]
2017-06-12 7:27 ` [LTP] [PATCH v2] syscalls/write01.c: Add test with different buffer sizes && Remove write02 Jinhui Huang
2017-06-13 10:59 ` Cyril Hrubis
2017-06-15 9:26 ` [LTP] [PATCH v3] " Jinhui Huang
2017-06-15 14:56 ` 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=20170526141655.GE6492@rei.lan \
--to=chrubis@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