From: Shuah Khan <skhan@linuxfoundation.org>
To: Iurii Zaikin <yzaikin@google.com>,
linux-kselftest@vger.kernel.org, linux-ext4@vger.kernel.org,
tytso@mit.edu, adilger.kernel@dilger.ca, Tim.Bird@sony.com
Cc: kunit-dev@googlegroups.com, brendanhiggins@google.com,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH linux-kselftest/test v6] ext4: add kunit test for decoding extended timestamps
Date: Thu, 17 Oct 2019 16:21:08 -0600 [thread overview]
Message-ID: <73ef528c-6424-351c-c07c-d0d5b4ebb02e@linuxfoundation.org> (raw)
In-Reply-To: <20191017221233.154848-1-yzaikin@google.com>
On 10/17/19 4:12 PM, Iurii Zaikin wrote:
> KUnit tests for decoding extended 64 bit timestamps that verify the
> seconds part of [a/c/m] timestamps in ext4 inode structs are decoded
> correctly.
>
> Test data is derived from the table in the Inode Timestamps section of
> Documentation/filesystems/ext4/inodes.rst.
>
> KUnit tests run during boot and output the results to the debug log
> in TAP format (http://testanything.org/). Only useful for kernel devs
> running KUnit test harness and are not for inclusion into a production
> build.
>
> Signed-off-by: Iurii Zaikin <yzaikin@google.com>
> Reviewed-by: Theodore Ts'o <tytso@mit.edu>
> Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
> Tested-by: Brendan Higgins <brendanhiggins@google.com>
Looks good.
Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
I plan to apply this to linux-kselftest/test
thanks,
-- Shuah
prev parent reply other threads:[~2019-10-17 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 22:12 [PATCH linux-kselftest/test v6] ext4: add kunit test for decoding extended timestamps Iurii Zaikin
2019-10-17 22:21 ` Shuah Khan [this message]
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=73ef528c-6424-351c-c07c-d0d5b4ebb02e@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=Tim.Bird@sony.com \
--cc=adilger.kernel@dilger.ca \
--cc=brendanhiggins@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yzaikin@google.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).