mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Paul Moore <paul@paul-moore.com>
Subject: linux-next: manual merge of the landlock tree with the security tree
Date: Tue, 20 Oct 2026 14:40:57 +0100	[thread overview]
Message-ID: <atdvaWI6T-HXhtix@sirena.co.uk> (raw)

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

Hi all,

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

  include/linux/ns/ns_common_types.h

between commit:

  436485132d236 ("Automated merge of 'lsm/dev' into 'stable-7.4'")

from the security tree and commit:

  0cbc5a0d65b05 ("Merge branch 'lsm/dev' into master")

from the landlock 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 --combined include/linux/ns/ns_common_types.h
index 47a5cfe2326a3,fddc62be3b626..0000000000000
--- a/include/linux/ns/ns_common_types.h
+++ b/include/linux/ns/ns_common_types.h
@@@ -116,11 -116,11 +116,11 @@@ struct ns_common 
  	struct dentry *stashed;
  	const struct proc_ns_operations *ops;
  	unsigned int inum;
 -	struct ns_tree;
 -	struct rcu_head ns_rcu;
  #ifdef CONFIG_SECURITY
  	void *ns_security;
  #endif
 +	struct ns_tree;
 +	struct rcu_head ns_rcu;
  };
  
  #define to_ns_common(__ns)                                    \

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

             reply	other threads:[~2026-10-20 13:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 13:40 Mark Brown [this message]
2026-10-20 14:13 ` Mickaël Salaün
2026-10-20 14:19   ` Mickaël Salaün

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=atdvaWI6T-HXhtix@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mic@digikod.net \
    --cc=paul@paul-moore.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®