From: Steve French <smfrench@gmail.com>
To: CIFS <linux-cifs@vger.kernel.org>, Xiaoli Feng <xifeng@redhat.com>
Subject: xfstests passing again to current for-next
Date: Tue, 5 Mar 2019 17:45:16 -0600 [thread overview]
Message-ID: <CAH2r5ms8C9cQSTY51neWvSRCahJ-dSMekZVza-9fA=LdZBY+qw@mail.gmail.com> (raw)
Moved the xfstest git branch back to December 6th (just before the
testcase problem patch Xiaoli pointed out) - and cherrypicked tests
524 and 528. Looks like current for-next worked fine
(http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/4/builds/111).
Will kick off the cifs-testing bucket later today.
--
Thanks,
Steve
next reply other threads:[~2019-03-05 23:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 23:45 Steve French [this message]
2019-03-06 0:26 ` xfstests passing again to current for-next Steve French
2019-03-06 1:16 ` Steve French
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='CAH2r5ms8C9cQSTY51neWvSRCahJ-dSMekZVza-9fA=LdZBY+qw@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=xifeng@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).