From: Jeremy Kerr <jk@ozlabs.org>
To: linux-kernel@vger.kernel.org
Cc: linux-efi@vger.kernel.org, Matt Fleming <matt.fleming@intel.com>,
Lingzhu Xiang <lxiang@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/3 v3] selftests: Add efivarfs tests
Date: Wed, 06 Feb 2013 22:48:08 +0800 [thread overview]
Message-ID: <1360162088.142733.191120808822.0.gpush@pecola> (raw)
In-Reply-To: <1360162088.142733.191120808822.0.gpush@pecola>
Hi all,
The following patches add a small set of tests to the
tools/testing/selftests directory. These cover some of the basic
functionality of efivarfs.
Comments welcome - changes 2 and 3 cover some behaviour that Matt and I
have discussed, but I'd appreciate any wider comment on the semantics
covered by these.
Cheers,
Jeremy
--
v2: Remove qemu check, add a couple of tests
v3: Change expected empty read() behaviour to return EOF
---
Jeremy Kerr (3):
selftests: Add tests for efivarfs
selftests/efivarfs: Add empty file creation test
selftests/efivarfs: Add create-read test
next parent reply other threads:[~2013-02-06 14:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 14:48 Jeremy Kerr [this message]
2013-02-06 14:48 ` [PATCH 2/3 v3] selftests/efivarfs: Add empty file creation test Jeremy Kerr
2013-02-06 14:48 ` [PATCH 1/3 v3] selftests: Add tests for efivarfs Jeremy Kerr
2013-02-07 23:13 ` Andrew Morton
2013-02-08 10:02 ` [PATCH] Documentation: Add a simple doc for selftests Jeremy Kerr
2013-02-12 23:56 ` Andrew Morton
2013-02-08 10:05 ` [PATCH 1/3 v3] selftests: Add tests for efivarfs Jeremy Kerr
2013-02-08 10:08 ` Matt Fleming
2013-02-12 23:50 ` Andrew Morton
2013-02-13 7:32 ` Matt Fleming
2013-02-12 23:48 ` Andrew Morton
2013-02-06 14:48 ` [PATCH 3/3 v3] selftests/efivarfs: Add create-read test Jeremy Kerr
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=1360162088.142733.191120808822.0.gpush@pecola \
--to=jk@ozlabs.org \
--cc=akpm@linux-foundation.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lxiang@redhat.com \
--cc=matt.fleming@intel.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
all inboxes | Powered by JetHome®