From d38e561588045d357743d3acd18dfa98e1923b1e Mon Sep 17 00:00:00 2001
From: David Sterba <dsterba@suse.com>
Date: Fri, 14 Oct 2022 12:48:47 +0200
Subject: [PATCH] btrfs-progs: docs: fix version when send v2 was introduced

As reported the documentation stated the send protocol v2 support was
supported since 5.18, but that's probably remnants of past revisions of
the patches introducing the support. Correct version is 6.0

Issue: #529
Signed-off-by: David Sterba <dsterba@suse.com>
---
 Documentation/btrfs-send.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/btrfs-send.rst b/Documentation/btrfs-send.rst
index 7df0fa75..413a27b3 100644
--- a/Documentation/btrfs-send.rst
+++ b/Documentation/btrfs-send.rst
@@ -68,8 +68,8 @@ please see section *SUBVOLUME FLAGS* in :doc:`btrfs-subvolume(8)<btrfs-subvolume
         The default is 1, which was the original protocol version. Version 2
         encodes file data slightly more efficiently; it is also required for
         sending compressed data directly (see *--compressed-data*). Version 2
-        requires at least btrfs-progs 5.18 on both the sender and receiver and
-        at least Linux 5.18 on the sender. Passing 0 means to use the highest
+        requires at least btrfs-progs 6.0 on both the sender and receiver and
+        at least Linux 6.0 on the sender. Passing 0 means to use the highest
         version supported by the running kernel.
 
 --compressed-data
@@ -77,7 +77,7 @@ please see section *SUBVOLUME FLAGS* in :doc:`btrfs-subvolume(8)<btrfs-subvolume
         decompressing it
 
         If the receiver supports the *BTRFS_IOC_ENCODED_WRITE* ioctl (added in
-        Linux 5.18), it can also write it directly without decompressing it.
+        Linux 6.0), it can also write it directly without decompressing it.
         Otherwise, the receiver will fall back to decompressing it and writing
         it normally.