public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Miguel Ojeda <ojeda@kernel•org>, Paul Moore <paul@paul-moore•com>
Cc: Alice Ryhl <aliceryhl@google•com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: manual merge of the rust tree with the security tree
Date: Mon, 16 Dec 2024 15:35:35 +1100	[thread overview]
Message-ID: <20241216153535.23d51bb8@canb.auug.org.au> (raw)

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

Hi all,

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

  rust/kernel/security.rs

between commit:

  9c76eaf78488 ("rust: replace lsm context+len with lsm_context")

from the security tree and commit:

  4724732dc2a8 ("rust: finish using custom FFI integer types")

from the rust tree.

I fixed it up (I just used the former) 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

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

             reply	other threads:[~2024-12-16  4:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16  4:35 Stephen Rothwell [this message]
2024-12-16 10:27 ` linux-next: manual merge of the rust tree with the security tree Miguel Ojeda

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=20241216153535.23d51bb8@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=aliceryhl@google$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=ojeda@kernel$(echo .)org \
    --cc=paul@paul-moore$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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