From: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
To: linux-modules@vger.kernel.org
Cc: ykaliuta@redhat.com, Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH kmod 0/2] testsuite: abstraction to compare file descriptor
Date: Fri, 4 Jan 2019 23:41:32 +0200 [thread overview]
Message-ID: <20190104214134.23971-1-yauheni.kaliuta@redhat.com> (raw)
Factor out common code to handle comparation of stdout/stderr to the
template.
The first patch is made to make reviewing of the change of the
original logic easier.
Yauheni Kaliuta (2):
testsuite: track number of descriptors instead of their state
testsuite: factor out fd related parameters to a structure
testsuite/testsuite.c | 362 +++++++++++++++++++++++++-----------------
1 file changed, 219 insertions(+), 143 deletions(-)
--
2.20.0
next reply other threads:[~2019-01-04 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 21:41 Yauheni Kaliuta [this message]
2019-01-04 21:41 ` [PATCH kmod 1/2] testsuite: track number of descriptors instead of their state Yauheni Kaliuta
2019-01-04 21:41 ` [PATCH kmod 2/2] testsuite: factor out fd related parameters to a structure Yauheni Kaliuta
2019-01-04 22:40 ` [PATCH kmod 0/2] testsuite: abstraction to compare file descriptor Lucas De Marchi
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=20190104214134.23971-1-yauheni.kaliuta@redhat.com \
--to=yauheni.kaliuta@redhat.com \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=ykaliuta@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).