From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@buildroot.org
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>
Subject: [Buildroot] [PATCH v2 2/2] package/nfs-utils: Update supported versions
Date: Sat, 22 Jan 2022 19:50:49 +0100 [thread overview]
Message-ID: <20220122185049.1194-2-petr.vorel@gmail.com> (raw)
In-Reply-To: <20220122185049.1194-1-petr.vorel@gmail.com>
Suggested-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
---
New in v2
package/nfs-utils/Config.in | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/package/nfs-utils/Config.in b/package/nfs-utils/Config.in
index df9c12ca44..f00debc420 100644
--- a/package/nfs-utils/Config.in
+++ b/package/nfs-utils/Config.in
@@ -12,6 +12,8 @@ config BR2_PACKAGE_NFS_UTILS
help
The NFS Linux kernel server.
+ Supports NFSv3 and optionally NFSv4 (and later).
+
http://linux-nfs.org/
if BR2_PACKAGE_NFS_UTILS
@@ -24,7 +26,7 @@ config BR2_PACKAGE_NFS_UTILS_NFSV4
select BR2_PACKAGE_LVM2
select BR2_PACKAGE_SQLITE
help
- Enable NFSv4/NFSv4.1 support
+ Enable NFSv4/NFSv4.1/NFSv4.2 support
comment "NFSv4/NFSv4.1 support needs a toolchain w/ dynamic library"
depends on BR2_STATIC_LIBS
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-22 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 18:50 [Buildroot] [PATCH v2 1/2] package/nfs-utils: bump version to 2.6.1 Petr Vorel
2022-01-22 18:50 ` Petr Vorel [this message]
2022-01-22 19:02 ` [Buildroot] [PATCH v2 2/2] package/nfs-utils: Update supported versions Giulio Benetti
2022-01-22 19:14 ` Yann E. MORIN
2022-01-22 19:35 ` Petr Vorel
2022-01-22 19:13 ` [Buildroot] [PATCH v2 1/2] package/nfs-utils: bump version to 2.6.1 Yann E. MORIN
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=20220122185049.1194-2-petr.vorel@gmail.com \
--to=petr.vorel@gmail.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.