linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Daniel Wagner <daniel.wagner@bmw-carit.de>,
	Daniel Wagner <wagi@monom.org>, <linux-nfs@vger.kernel.org>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] NFS: Use complete() instead complete_all()
Date: Tue, 27 Sep 2016 13:15:19 -0400	[thread overview]
Message-ID: <f7075c3b-c640-e7ee-7dfb-2c37ff1a3caa@Netapp.com> (raw)
In-Reply-To: <99846ad0-6b62-0bc4-f03b-cdc98b702af5@bmw-carit.de>

On 09/27/2016 04:33 AM, Daniel Wagner wrote:
> On 09/27/2016 09:42 AM, Daniel Wagner wrote:
>> Failures: generic/035 generic/087 generic/088 generic/089 generic/126 generic/184 generic/285 generic/347 generic/350
>> Failed 9 of 62 tests
>>
>> Hmm, not sure if this good or bad. Does it help?
> 
> FWIW, running the same tests on non patched kernel gives the same result:

Thanks for testing!  If it has the same results before and after your patches then you should be good :).  I've seen different sets of failed tests for different underlying filesystems, so I don't think it's a big deal that we have different failed tests here.

Thanks again,
Anna

> 
> Failures: generic/035 generic/087 generic/088 generic/089 generic/126 generic/184 generic/285 generic/347 generic/350
> Failed 9 of 62 tests
> 
> 
> 


  reply	other threads:[~2016-09-27 17:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 11:54 [PATCH 0/2] NFS: Use complete() instead complete_all() Daniel Wagner
2016-09-22 11:54 ` [PATCH 1/2] NFS: direct: use complete() instead of complete_all() Daniel Wagner
2016-09-22 11:54 ` [PATCH 2/2] NFS: cache_lib: " Daniel Wagner
2016-09-23 13:48 ` [PATCH 0/2] NFS: Use complete() instead complete_all() Anna Schumaker
2016-09-26  5:33   ` Daniel Wagner
2016-09-26 13:31     ` Anna Schumaker
2016-09-27  7:42       ` Daniel Wagner
2016-09-27  8:33         ` Daniel Wagner
2016-09-27 17:15           ` Anna Schumaker [this message]
2016-09-27 17:18           ` Anna Schumaker

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=f7075c3b-c640-e7ee-7dfb-2c37ff1a3caa@Netapp.com \
    --to=anna.schumaker@netapp.com \
    --cc=daniel.wagner@bmw-carit.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    --cc=wagi@monom.org \
    /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).