public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Christian Brauner <brauner@kernel.org>
Cc: Alice Ryhl <aliceryhl@google.com>, Daniel Xu <dxu@dxuuu.xyz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Wedson Almeida Filho <wedsonaf@gmail.com>
Subject: linux-next: manual merge of the ftrace tree with the vfs-brauner tree
Date: Fri, 8 Nov 2024 13:55:04 +1100	[thread overview]
Message-ID: <20241108135504.519ce71e@canb.auug.org.au> (raw)

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

Hi all,

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

  rust/helpers/helpers.c

between commit:

  851849824bb5 ("rust: file: add Rust abstraction for `struct file`")

from the vfs-brauner tree and commit:

  6e59bcc9c8ad ("rust: add static_branch_unlikely for static_key_false")

from the ftrace 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 rust/helpers/helpers.c
index d553ad9361ce,17e1b60d178f..000000000000
--- a/rust/helpers/helpers.c
+++ b/rust/helpers/helpers.c
@@@ -11,9 -11,8 +11,10 @@@
  #include "bug.c"
  #include "build_assert.c"
  #include "build_bug.c"
 +#include "cred.c"
  #include "err.c"
 +#include "fs.c"
+ #include "jump_label.c"
  #include "kunit.c"
  #include "mutex.c"
  #include "page.c"

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

             reply	other threads:[~2024-11-08  2:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08  2:55 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-17  3:21 linux-next: manual merge of the ftrace tree with the vfs-brauner tree Stephen Rothwell
2024-07-19  0:34 ` Stephen Rothwell
2024-06-13  1:42 Stephen Rothwell
2024-06-13  7:07 ` Jiri Olsa
2024-06-13 23:05   ` Stephen Rothwell
2024-06-14  1:07     ` Masami Hiramatsu
2024-07-02 17:06       ` Stephen Rothwell

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=20241108135504.519ce71e@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=aliceryhl@google.com \
    --cc=brauner@kernel.org \
    --cc=dxu@dxuuu.xyz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=wedsonaf@gmail.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