linux-kernel - linux-next: manual merge of 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: <20200303102523.0b3b4e52@canb.auug.org.au>
Date:   Tue, 3 Mar 2020 10:25:23 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Jonathan Corbet <corbet@....net>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Randy Dunlap <rdunlap@...radead.org>,
        Damien Le Moal <damien.lemoal@....com>,
        Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Subject: linux-next: manual merge of the jc_docs tree with Linus' tree

Hi all,

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

  Documentation/filesystems/zonefs.rst

between commit:

  4c5fd3b791a0 ("zonefs: fix documentation typos etc.")

from Linus' tree and commit:

  9a6108124c1d ("docs: filesystems: convert zonefs.txt to ReST")

from the jc_docs 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/filesystems/zonefs.rst
index d54fa98ac158,7e733e751e98..000000000000
--- a/Documentation/filesystems/zonefs.rst
+++ b/Documentation/filesystems/zonefs.rst
@@@ -301,7 -308,8 +308,8 @@@ Mount option
  
  zonefs define the "errors=<behavior>" mount option to allow the user to specify
  zonefs behavior in response to I/O errors, inode size inconsistencies or zone
 -condition chages. The defined behaviors are as follow:
 +condition changes. The defined behaviors are as follow:
+ 
  * remount-ro (default)
  * zone-ro
  * zone-offline

Content of type "application/pgp-signature" skipped