All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miguel Ojeda <ojeda@kernel.org>
To: akpm@linux-foundation.org
Cc: aliceryhl@google.com, edumazet@google.com,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	ojeda@kernel.org, sfr@canb.auug.org.au, wedsonaf@gmail.com
Subject: Re: linux-next: build failure after merge of the mm-nonmm-unstable tree
Date: Thu, 20 Nov 2025 09:55:18 +0100	[thread overview]
Message-ID: <20251120085518.1463498-1-ojeda@kernel.org> (raw)
In-Reply-To: <20251119154824.339bfbeb47d149b041f15550@linux-foundation.org>

On Wed, 19 Nov 2025 15:48:24 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> Thanks, I'll disable them for now.
>
> Alice, can you please help us with a fix?  Simple patch follows:

Something like this should work (I would suggest adding each helper into
the right commit that performs each move to the header):

diff --git a/rust/helpers/rbtree.c b/rust/helpers/rbtree.c
index 6d404b84a9b5..2a0eabbb4160 100644
--- a/rust/helpers/rbtree.c
+++ b/rust/helpers/rbtree.c
@@ -7,3 +7,13 @@ void rust_helper_rb_link_node(struct rb_node *node, struct rb_node *parent,
 {
        rb_link_node(node, parent, rb_link);
 }
+
+struct rb_node *rust_helper_rb_first(const struct rb_root *root)
+{
+       return rb_first(root);
+}
+
+struct rb_node *rust_helper_rb_last(const struct rb_root *root)
+{
+       return rb_last(root);
+}

Cheers,
Miguel

  reply	other threads:[~2025-11-20  8:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-16 23:23 linux-next: build failure after merge of the mm-nonmm-unstable tree Stephen Rothwell
2025-11-19 23:14 ` Stephen Rothwell
2025-11-19 23:48   ` Andrew Morton
2025-11-20  8:55     ` Miguel Ojeda [this message]
2025-11-20 10:01     ` Alice Ryhl
  -- strict thread matches above, loose matches on Subject: below --
2026-04-29  9:10 Thierry Reding
2026-03-17 14:32 Mark Brown
2026-03-17 15:06 ` Mathieu Desnoyers
2026-03-17 15:07   ` David CARLIER
2026-02-16 13:58 Mark Brown
2025-12-18  4:30 Stephen Rothwell
2025-12-21  2:58 ` Finn Thain
2025-12-26 16:45   ` Sasha Levin
2025-12-29  8:56     ` Finn Thain
2026-01-01  9:21       ` Finn Thain
2026-01-01 17:01         ` Randy Dunlap
2026-01-01 23:15           ` Finn Thain
2026-01-02  7:29     ` Ard Biesheuvel
2026-01-02 22:09       ` Finn Thain
2025-11-16 22:36 Stephen Rothwell
2025-10-17 13:25 Mark Brown
2025-10-17 21:34 ` Andrew Morton
2025-09-01  1:17 Stephen Rothwell
2025-07-11  0:58 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=20251120085518.1463498-1-ojeda@kernel.org \
    --to=ojeda@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=aliceryhl@google.com \
    --cc=edumazet@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.