diff --git a/doc/FAQ.md b/doc/FAQ.md
index 48f2c1a..8e1801f 100644
--- a/doc/FAQ.md
+++ b/doc/FAQ.md
@@ -205,12 +205,6 @@ effect, this also detects possible read-errors on your backup targets
 
 See **btrbk archive** command in [btrbk(1)] for more details.
 
-**Note that kernels >=4.1 and <4.4 have a bug when re-sending
-subvolumes**, make sure you run a recent/patched kernel or step 3 will
-fail. Read
-[this thread on gmane](http://thread.gmane.org/gmane.comp.file-systems.btrfs/48798)
-(the patch provided is confirmed working on kernels 4.2.x and 4.3.x).
-
 
 ### Answer 2: Use external storage as "stream-fifo"
 
diff --git a/doc/btrbk.1.asciidoc b/doc/btrbk.1.asciidoc
index 18e1357..60b0da9 100644
--- a/doc/btrbk.1.asciidoc
+++ b/doc/btrbk.1.asciidoc
@@ -227,16 +227,11 @@ retention policy).
     continue using btrbk after swapping your backup disk with the
     archive disk.
 +
-Note that this feature needs a *linux kernel >=4.4* to work correctly!
-Kernels >=4.1 and <4.4 have a bug when re-sending subvolumes (the
-archived subvolumes will have incorrect received_uuid, see
-<http://thread.gmane.org/gmane.comp.file-systems.btrfs/48798>), so
-make sure you run a recent kernel.
+If you want to use nested subvolumes on the target filesystem, you
+need to create them by hand (e.g. by running "btrfs subvolume create
+<target>/dir"). Check the output of --dry-run if unsure.
 +
-Known bugs: If you want to use nested subvolumes on the target
-filesystem, you need to create them by hand (e.g. by running "btrfs
-subvolume create <target>/dir"). Check the output of --dry-run if
-unsure.
+Note that this feature needs a *linux kernel >=4.4* to work correctly!
 
 *clean* [filter...]::
     Delete incomplete (garbled) backups. Incomplete backups can be