linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: manual merge of the jc_docs tree with Linus' tree
@ 2019-05-09  0:44 Stephen Rothwell
  0 siblings, 0 replies; 8+ messages in thread
From: Stephen Rothwell @ 2019-05-09  0:44 UTC (permalink / raw)
  To: Jonathan Corbet
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Stephen Kitt,
	Ingo Molnar, Changbin Du

[-- Attachment #1: Type: text/plain, Size: 3624 bytes --]

Hi Jon,

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

  Documentation/x86/x86_64/mm.txt

between commit:

  89502a019790 ("x86/mm: Fix the 56-bit addresses memory map in Documentation/x86/x86_64/mm.txt")

from Linus' tree and commit:

  b88679d2f2b9 ("Documentation: x86: convert x86_64/mm.txt to reST")

from the jc_docs tree.

I fixed it up (I deleted the file and added teh following patch) 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.

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Thu, 9 May 2019 10:39:31 +1000
Subject: [PATCH] Documentation: x86: update for "x86/mm: Fix the 56-bit
 addresses memory map in Documentation/x86/x86_64/mm.txt"

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 Documentation/x86/x86_64/mm.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/x86/x86_64/mm.rst b/Documentation/x86/x86_64/mm.rst
index 52020577b8de..267fc4808945 100644
--- a/Documentation/x86/x86_64/mm.rst
+++ b/Documentation/x86/x86_64/mm.rst
@@ -78,7 +78,7 @@ Complete virtual memory map with 5-level page tables
 .. note::
 
  - With 56-bit addresses, user-space memory gets expanded by a factor of 512x,
-   from 0.125 PB to 64 PB. All kernel mappings shift down to the -64 PT starting
+   from 0.125 PB to 64 PB. All kernel mappings shift down to the -64 PB starting
    offset and many of the regions expand to support the much larger physical
    memory supported.
 
@@ -91,7 +91,7 @@ Complete virtual memory map with 5-level page tables
    0000000000000000 |    0       | 00ffffffffffffff |   64 PB | user-space virtual memory, different per mm
   __________________|____________|__________________|_________|___________________________________________________________
                     |            |                  |         |
-   0000800000000000 |  +64    PB | ffff7fffffffffff | ~16K PB | ... huge, still almost 64 bits wide hole of non-canonical
+   0100000000000000 |  +64    PB | feffffffffffffff | ~16K PB | ... huge, still almost 64 bits wide hole of non-canonical
                     |            |                  |         |     virtual memory addresses up to the -64 PB
                     |            |                  |         |     starting offset of kernel mappings.
   __________________|____________|__________________|_________|___________________________________________________________
@@ -107,7 +107,7 @@ Complete virtual memory map with 5-level page tables
    ffd2000000000000 |  -11.5  PB | ffd3ffffffffffff |  0.5 PB | ... unused hole
    ffd4000000000000 |  -11    PB | ffd5ffffffffffff |  0.5 PB | virtual memory map (vmemmap_base)
    ffd6000000000000 |  -10.5  PB | ffdeffffffffffff | 2.25 PB | ... unused hole
-   ffdf000000000000 |   -8.25 PB | fffffdffffffffff |   ~8 PB | KASAN shadow memory
+   ffdf000000000000 |   -8.25 PB | fffffbffffffffff |   ~8 PB | KASAN shadow memory
   __________________|____________|__________________|_________|____________________________________________________________
                                                               |
                                                               | Identical layout to the 47-bit one from here on:
-- 
2.20.1

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply related	[flat|nested] 8+ messages in thread

* linux-next: manual merge of the jc_docs tree with Linus' tree
@ 2020-03-22 23:50 Stephen Rothwell
  0 siblings, 0 replies; 8+ messages in thread
From: Stephen Rothwell @ 2020-03-22 23:50 UTC (permalink / raw)
  To: Jonathan Corbet
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Tyler Hicks,
	Lukas Bulwahn

[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

Hi all,

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

  MAINTAINERS

between commit:

  726464596b5d ("MAINTAINERS: eCryptfs: Update maintainer address and downgrade status")

from Linus' tree and commit:

  19e91e543c82 ("MAINTAINERS: adjust to filesystem doc ReST conversion")

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 MAINTAINERS
index 8882742b0f5b,38f58b85eb06..000000000000
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@@ -3917,10 -3906,10 +3917,10 @@@ W:	http://ceph.com
  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git
  T:	git git://github.com/ceph/ceph-client.git
  S:	Supported
- F:	Documentation/filesystems/ceph.txt
+ F:	Documentation/filesystems/ceph.rst
  F:	fs/ceph/
  
 -CERTIFICATE HANDLING:
 +CERTIFICATE HANDLING
  M:	David Howells <dhowells@redhat.com>
  M:	David Woodhouse <dwmw2@infradead.org>
  L:	keyrings@vger.kernel.org
@@@ -5948,8 -5937,8 +5948,8 @@@ L:	ecryptfs@vger.kernel.or
  W:	http://ecryptfs.org
  W:	https://launchpad.net/ecryptfs
  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git
 -S:	Supported
 +S:	Odd Fixes
- F:	Documentation/filesystems/ecryptfs.txt
+ F:	Documentation/filesystems/ecryptfs.rst
  F:	fs/ecryptfs/
  
  EDAC-AMD64

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* linux-next: manual merge of the jc_docs tree with Linus' tree
@ 2020-03-02 23:25 Stephen Rothwell
  0 siblings, 0 replies; 8+ messages in thread
From: Stephen Rothwell @ 2020-03-02 23:25 UTC (permalink / raw)
  To: Jonathan Corbet
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Randy Dunlap,
	Damien Le Moal, Mauro Carvalho Chehab

[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]

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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* linux-next: manual merge of the jc_docs tree with Linus' tree
@ 2019-07-25  0:26 Stephen Rothwell
  0 siblings, 0 replies; 8+ messages in thread
From: Stephen Rothwell @ 2019-07-25  0:26 UTC (permalink / raw)
  To: Jonathan Corbet
  Cc: Linux Next Mailing List, Linux Kernel Mailing List,
	Christoph Hellwig, Paolo Bonzini, Mauro Carvalho Chehab

[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]

Hi all,

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

  MAINTAINERS

between commit:

  2f5947dfcaec ("Documentation: move Documentation/virtual to Documentation/virt")

from Linus' tree and commit:

  bff9e34c6785 ("docs: fix broken doc references due to renames")

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 MAINTAINERS
index 641ff29be1a5,ff3ae2be2746..d376dc0c7b68
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@@ -12136,7 -12137,7 +12136,7 @@@ M:	Thomas Hellstrom <thellstrom@vmware.
  M:	"VMware, Inc." <pv-drivers@vmware.com>
  L:	virtualization@lists.linux-foundation.org
  S:	Supported
- F:	Documentation/virt/paravirt_ops.txt
 -F:	Documentation/virtual/paravirt_ops.rst
++F:	Documentation/virt/paravirt_ops.rst
  F:	arch/*/kernel/paravirt*
  F:	arch/*/include/asm/paravirt*.h
  F:	include/linux/hypervisor.h

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* linux-next: manual merge of the jc_docs tree with Linus' tree
@ 2017-10-31 23:35 Stephen Rothwell
  0 siblings, 0 replies; 8+ messages in thread
From: Stephen Rothwell @ 2017-10-31 23:35 UTC (permalink / raw)
  To: Jonathan Corbet
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Greg Kroah-Hartman

Hi Jon,

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

  Documentation/process/index.rst

between commit:

  9ed95129ffca ("Documentation: Add a file explaining the Linux kernel license enforcement policy")

from Linus' tree and commit:

  13277782dd4b ("Documentation: add Kernel Driver Statement to the kernel")

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/process/index.rst
index 61e43cc3ed17,68454319f006..000000000000
--- a/Documentation/process/index.rst
+++ b/Documentation/process/index.rst
@@@ -25,7 -25,7 +25,8 @@@ Below are the essential guides that eve
     submitting-patches
     coding-style
     email-clients
 +   kernel-enforcement-statement
+    kernel-driver-statement
  
  Other guides to the community that are of interest to most developers are: 
  

^ permalink raw reply	[flat|nested] 8+ messages in thread

* linux-next: manual merge of the jc_docs tree with Linus' tree
@ 2017-10-19 11:32 Mark Brown
  0 siblings, 0 replies; 8+ messages in thread
From: Mark Brown @ 2017-10-19 11:32 UTC (permalink / raw)
  To: Jonathan Corbet, Greg Kroah-Hartman, Mauro Carvalho Chehab
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]

Hi Jonathan,

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

  Documentation/process/index.rst

between commit:

  9ed95129ffcab ("Documentation: Add a file explaining the Linux kernel license enforcement policy")

from Linus' tree and commit:

  13277782dd4bc ("Documentation: add Kernel Driver Statement to the kernel")

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.

diff --cc Documentation/process/index.rst
index 61e43cc3ed17,68454319f006..000000000000
--- a/Documentation/process/index.rst
+++ b/Documentation/process/index.rst
@@@ -25,7 -25,7 +25,8 @@@ Below are the essential guides that eve
     submitting-patches
     coding-style
     email-clients
 +   kernel-enforcement-statement
+    kernel-driver-statement
  
  Other guides to the community that are of interest to most developers are: 
  

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* linux-next: manual merge of the jc_docs tree with Linus' tree
@ 2016-08-05  2:42 Stephen Rothwell
  0 siblings, 0 replies; 8+ messages in thread
From: Stephen Rothwell @ 2016-08-05  2:42 UTC (permalink / raw)
  To: Jonathan Corbet
  Cc: linux-next, linux-kernel, Jani Nikula, Mauro Carvalho Chehab

Hi Jon,

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

  Documentation/DocBook/Makefile

between commit:

  43f71d93a0cb ("doc-rst: Remove the media docbook")

from Linus' tree and commit:

  bdf107d87eb8 ("DocBook: use DOCBOOKS="" to ignore DocBooks instead of IGNORE_DOCBOOKS=1")

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/DocBook/Makefile
index c481df33ef21,fb32ab85ea3a..000000000000
--- a/Documentation/DocBook/Makefile
+++ b/Documentation/DocBook/Makefile
@@@ -16,9 -14,19 +14,17 @@@ DOCBOOKS := z8530book.xml device-driver
  	    genericirq.xml s390-drivers.xml uio-howto.xml scsi.xml \
  	    80211.xml debugobjects.xml sh.xml regulator.xml \
  	    alsa-driver-api.xml writing-an-alsa-driver.xml \
 -	    tracepoint.xml gpu.xml media_api.xml w1.xml \
 +	    tracepoint.xml w1.xml \
  	    writing_musb_glue_layer.xml crypto-API.xml iio.xml
  
+ ifeq ($(DOCBOOKS),)
+ 
+ # Skip DocBook build if the user explicitly requested no DOCBOOKS.
+ .DEFAULT:
+ 	@echo "  SKIP    DocBook $@ target (DOCBOOKS=\"\" specified)."
+ 
+ else
+ 
 -include Documentation/DocBook/media/Makefile
 -
  ###
  # The build process is as follows (targets):
  #              (xmldocs) [by docproc]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* linux-next: manual merge of the jc_docs tree with Linus' tree
@ 2015-10-12  2:38 Stephen Rothwell
  0 siblings, 0 replies; 8+ messages in thread
From: Stephen Rothwell @ 2015-10-12  2:38 UTC (permalink / raw)
  To: Jonathan Corbet
  Cc: linux-next, linux-kernel, David Howells, Benoit Lemarchand

Hi Jonathan,

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

  Documentation/Changes

between commit:

  283e8ba2dfde ("MODSIGN: Change from CMS to PKCS#7 signing if the openssl is too old")

from Linus' tree and commit:

  1c3a54e257f7 ("Documentation/Changes: Add bc in "Current Minimal Requirements" section")

from the jc_docs tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc Documentation/Changes
index f447f0516f07,268a849c4cc0..000000000000
--- a/Documentation/Changes
+++ b/Documentation/Changes
@@@ -43,7 -43,8 +43,8 @@@ o  udev                   08
  o  grub                   0.93                    # grub --version || grub-install --version
  o  mcelog                 0.6                     # mcelog --version
  o  iptables               1.4.2                   # iptables -V
 -o  openssl & libcrypto    1.0.1k                  # openssl version
 +o  openssl & libcrypto    1.0.0                   # openssl version
+ o  bc                     1.06.95                 # bc --version
  
  
  Kernel compilation

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2020-03-22 23:50 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-09  0:44 linux-next: manual merge of the jc_docs tree with Linus' tree Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2020-03-22 23:50 Stephen Rothwell
2020-03-02 23:25 Stephen Rothwell
2019-07-25  0:26 Stephen Rothwell
2017-10-31 23:35 Stephen Rothwell
2017-10-19 11:32 Mark Brown
2016-08-05  2:42 Stephen Rothwell
2015-10-12  2:38 Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).