linux-kernel - linux-next: manual merge of the device-mapper tree with the jc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20190704135805.6b077b57@canb.auug.org.au>
Date:   Thu, 4 Jul 2019 13:58:05 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Alasdair G Kergon <agk@...hat.com>,
        Mike Snitzer <snitzer@...hat.com>,
        Jonathan Corbet <corbet@....net>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Mauro Carvalho Chehab <mchehab+samsung@...nel.org>
Subject: linux-next: manual merge of the device-mapper tree with the jc_docs
 tree

Hi all,

Today's linux-next merge of the device-mapper tree got a conflict in:

  Documentation/device-mapper/snapshot.rst

between commit:

  f0ba43774cea ("docs: convert docs to ReST and rename to *.rst")

from the jc_docs tree and commit:

  a8a9f1434a86 ("dm snapshot: add optional discard support features")

from the device-mapper tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc Documentation/device-mapper/snapshot.rst
index 4c53304e72f1,1810833f6dc6..000000000000
--- a/Documentation/device-mapper/snapshot.rst
+++ b/Documentation/device-mapper/snapshot.rst
@@@ -31,7 -30,8 +31,8 @@@ original data will be saved in the <CO
  its visible content unchanged, at least until the <COW device> fills up.

 -*) snapshot <origin> <COW device> <persistent?> <chunksize>
 +-  snapshot <origin> <COW device> <persistent?> <chunksize>
+    [<# feature args> [<arg>]*]

  A snapshot of the <origin> block device is created. Changed chunks of
  <chunksize> sectors will be stored on the <COW device>.  Writes will

Content of type "application/pgp-signature" skipped