From: Guillaume Gardet <guillaume.gardet@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] net: NFS: Add NFSv3 support
Date: Fri, 24 Jun 2016 09:45:38 +0200 [thread overview]
Message-ID: <576CE522.4060404@free.fr> (raw)
In-Reply-To: <20160623190826.GY19080@bill-the-cat>
Le 23/06/2016 21:08, Tom Rini a ?crit :
> On Thu, Jun 23, 2016 at 11:10:26AM +0200, Guillaume GARDET wrote:
>
>> This patch enables NFSv3 support.
>> If NFSv2 is available use it as usual.
>> If NFSv2 is not available, but NFSv3 is available, use NFSv3.
>> If NFSv2 and NFSv3 are not available, print an error message since NFSv4 is not supported.
>>
>> Tested on iMX6 sabrelite with 4 Linux NFS servers:
>> * NFSv2 + NFSv3 + NFSv4 server: use NFSv2 protocol
>> * NFSv2 + NFSv3 server: use NFSv3 protocol
>> * NFSv3 + NFSv4 server: use NFSv3 protocol
>> * NFSv3 server: use NFSv3 protocol
> So, why do we have v2+v3+v4 -> v2 and not v2+v3+v4 -> v3, when we do
> v2+v3 -> v3 and v3+v4 -> v3 ? We should be consistent in preferring
> either v2 over v3 or v3 over v2. Thanks!
>
Sorry, it is a typo error. Please read: "NFSv2 + NFSv3 server: use NFSv2 protocol".
As long as NFSv2 is available, we use it. Otherwise, we use v3 if available. As explained above.
Guillaume
next prev parent reply other threads:[~2016-06-24 7:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 19:27 [U-Boot] [PATCH] net: NFS: Add NFSv3 support Guillaume GARDET
2016-06-20 19:31 ` Guillaume Gardet
2016-06-20 21:43 ` Joe Hershberger
2016-06-21 8:42 ` Guillaume Gardet
2016-06-23 9:10 ` [U-Boot] [PATCH V2] " Guillaume GARDET
2016-06-23 19:08 ` Tom Rini
2016-06-24 7:45 ` Guillaume Gardet [this message]
2016-06-24 15:03 ` Tom Rini
2016-06-25 19:26 ` Joe Hershberger
2016-07-20 9:48 ` Guillaume Gardet
2016-07-29 9:31 ` [U-Boot] [PATCH V3] " Guillaume GARDET
2016-07-29 14:07 ` Joe Hershberger
2016-08-23 2:28 ` [U-Boot] " Joe Hershberger
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=576CE522.4060404@free.fr \
--to=guillaume.gardet@free.fr \
--cc=u-boot@lists.denx.de \
/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