linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: manual merge of the security tree with the jc_docs tree
@ 2023-12-11  1:29 Stephen Rothwell
  2024-01-10  0:12 ` Stephen Rothwell
  0 siblings, 1 reply; 4+ messages in thread
From: Stephen Rothwell @ 2023-12-11  1:29 UTC (permalink / raw)
  To: Paul Moore, Jonathan Corbet
  Cc: Casey Schaufler, Kees Cook, Linux Kernel Mailing List,
	Linux Next Mailing List, Sumit Garg

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

Hi all,

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

  Documentation/userspace-api/index.rst

between commit:

  50709576d81b ("Documentation: Destage TEE subsystem documentation")

from the jc_docs tree and commit:

  f3b8788cde61 ("LSM: Identify modules by more than name")

from the security 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/userspace-api/index.rst
index 93174ffc7350,8be8b1979194..000000000000
--- a/Documentation/userspace-api/index.rst
+++ b/Documentation/userspace-api/index.rst
@@@ -30,7 -33,7 +30,8 @@@ place where this information is gathere
     sysfs-platform_profile
     vduse
     futex2
 +   tee
+    lsm
  
  .. only::  subproject and html
  

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

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

* Re: linux-next: manual merge of the security tree with the jc_docs tree
  2023-12-11  1:29 linux-next: manual merge of the security tree with the jc_docs tree Stephen Rothwell
@ 2024-01-10  0:12 ` Stephen Rothwell
  0 siblings, 0 replies; 4+ messages in thread
From: Stephen Rothwell @ 2024-01-10  0:12 UTC (permalink / raw)
  To: Jonathan Corbet
  Cc: Paul Moore, Casey Schaufler, Kees Cook,
	Linux Kernel Mailing List, Linux Next Mailing List, Sumit Garg

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

Hi all,

On Mon, 11 Dec 2023 12:29:17 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Today's linux-next merge of the security tree got a conflict in:
> 
>   Documentation/userspace-api/index.rst
> 
> between commit:
> 
>   50709576d81b ("Documentation: Destage TEE subsystem documentation")
> 
> from the jc_docs tree and commit:
> 
>   f3b8788cde61 ("LSM: Identify modules by more than name")
> 
> from the security 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/userspace-api/index.rst
> index 93174ffc7350,8be8b1979194..000000000000
> --- a/Documentation/userspace-api/index.rst
> +++ b/Documentation/userspace-api/index.rst
> @@@ -30,7 -33,7 +30,8 @@@ place where this information is gathere
>      sysfs-platform_profile
>      vduse
>      futex2
>  +   tee
> +    lsm
>   
>   .. only::  subproject and html
>   

This is now a conflict between the jc_docs tree and Linus' tree.

-- 
Cheers,
Stephen Rothwell

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

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

* Re: linux-next: manual merge of the security tree with the jc_docs tree
  2024-01-05  2:11 Stephen Rothwell
@ 2024-01-10  0:13 ` Stephen Rothwell
  0 siblings, 0 replies; 4+ messages in thread
From: Stephen Rothwell @ 2024-01-10  0:13 UTC (permalink / raw)
  To: Jonathan Corbet
  Cc: Paul Moore, Casey Schaufler, Kees Cook,
	Linux Kernel Mailing List, Linux Next Mailing List,
	Vegard Nossum

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

Hi all,

On Fri, 5 Jan 2024 13:11:40 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Today's linux-next merge of the security tree got a conflict in:
> 
>   Documentation/userspace-api/index.rst
> 
> between commits:
> 
>   77e075579e88 ("Documentation: move driver-api/isapnp to userspace-api/")
>   bb67bf1c4a56 ("Documentation: move driver-api/dcdbas to userspace-api/")
> 
> from the jc_docs tree and commit:
> 
>   f3b8788cde61 ("LSM: Identify modules by more than name")
> 
> from the security 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/userspace-api/index.rst
> index 74bc0716432e,8be8b1979194..000000000000
> --- a/Documentation/userspace-api/index.rst
> +++ b/Documentation/userspace-api/index.rst
> @@@ -30,9 -33,7 +30,10 @@@ place where this information is gathere
>      sysfs-platform_profile
>      vduse
>      futex2
>  +   tee
>  +   isapnp
>  +   dcdbas
> +    lsm
>   
>   .. only::  subproject and html
>   

This is now a conflict between the jc_docs tree and Linus' tree.

-- 
Cheers,
Stephen Rothwell

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

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

* linux-next: manual merge of the security tree with the jc_docs tree
@ 2024-01-05  2:11 Stephen Rothwell
  2024-01-10  0:13 ` Stephen Rothwell
  0 siblings, 1 reply; 4+ messages in thread
From: Stephen Rothwell @ 2024-01-05  2:11 UTC (permalink / raw)
  To: Paul Moore, Jonathan Corbet
  Cc: Casey Schaufler, Kees Cook, Linux Kernel Mailing List,
	Linux Next Mailing List, Vegard Nossum

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

Hi all,

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

  Documentation/userspace-api/index.rst

between commits:

  77e075579e88 ("Documentation: move driver-api/isapnp to userspace-api/")
  bb67bf1c4a56 ("Documentation: move driver-api/dcdbas to userspace-api/")

from the jc_docs tree and commit:

  f3b8788cde61 ("LSM: Identify modules by more than name")

from the security 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/userspace-api/index.rst
index 74bc0716432e,8be8b1979194..000000000000
--- a/Documentation/userspace-api/index.rst
+++ b/Documentation/userspace-api/index.rst
@@@ -30,9 -33,7 +30,10 @@@ place where this information is gathere
     sysfs-platform_profile
     vduse
     futex2
 +   tee
 +   isapnp
 +   dcdbas
+    lsm
  
  .. only::  subproject and html
  

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

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

end of thread, other threads:[~2024-01-10  0:13 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-12-11  1:29 linux-next: manual merge of the security tree with the jc_docs tree Stephen Rothwell
2024-01-10  0:12 ` Stephen Rothwell
2024-01-05  2:11 Stephen Rothwell
2024-01-10  0:13 ` 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).