From: Christoph Hellwig <hch@lst.de>
To: Huang Ying <ying.huang@intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [nfs] mount.nfs: an incorrect mount option was specified
Date: Mon, 9 Feb 2015 15:33:20 +0100 [thread overview]
Message-ID: <20150209143320.GA17820@lst.de> (raw)
In-Reply-To: <1423470942.5968.72.camel@intel.com>
On Mon, Feb 09, 2015 at 04:35:42PM +0800, Huang Ying wrote:
> FYI, we noticed the below changes on
>
> git://git.infradead.org/users/hch/pnfs.git pnfs-testing
> commit 418f5019f1a8cd6fc50db11303e5a9297522d814 ("nfs: force version 4.1")
>
> Our test script uses the following command line:
>
> $ mount.nfs -o v3,nolock <nfs service> <directory>
>
> And found something as follow in the stderr after the commit
>
> mount.nfs: an incorrect mount option was specified
This is a testing branch not really intended for Linux, and this
is a side effect. CAn you drop this branch (just the branch, and not the
repository) from the automated testing?
prev parent reply other threads:[~2015-02-09 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 8:35 [LKP] [nfs] mount.nfs: an incorrect mount option was specified Huang Ying
2015-02-09 14:33 ` Christoph Hellwig [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=20150209143320.GA17820@lst.de \
--to=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ying.huang@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