mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Greg KH <greg@kroah.com>, Arnd Bergmann <arnd@arndb.de>
Cc: Alice Ryhl <aliceryhl@google.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Miguel Ojeda <ojeda@kernel.org>
Subject: linux-next: manual merge of the char-misc tree with the rust tree
Date: Tue, 20 Oct 2026 13:27:34 +0100	[thread overview]
Message-ID: <atdeNvRKFuQd2qHz@sirena.co.uk> (raw)

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

Hi all,

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

  drivers/android/binder/thread.rs

between commit:

  a12f22b2c9398 ("rust_binder: use pr_*_ratelimited! for printing")

from the rust tree and commit:

  985955d8e6b2b ("rust_binder: wake epoll on self-work queued to poll thread")

from the char-misc 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 --cc drivers/android/binder/thread.rs
index e0ed20f510fd1,177e90a1e5a3f..0000000000000
--- a/drivers/android/binder/thread.rs
+++ b/drivers/android/binder/thread.rs
@@@ -344,13 -345,13 +345,13 @@@ impl InnerThread 
          }
      }
  
-     fn push_return_work(&mut self, reply: u32) {
+     fn push_return_work(&mut self, reply: u32) -> PushWorkRes {
          if let Ok(work) = ListArc::try_from_arc(self.return_work.clone()) {
              work.set_error_code(reply);
-             // Not notifying: Reply to current thread.
-             let _ = self.push_work(work);
+             self.push_work(work)
          } else {
 -            pr_warn!("Thread return work is already in use.");
 +            pr_warn_ratelimited!("Thread return work is already in use.\n");
+             PushWorkRes::Ok
          }
      }
  

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

             reply	other threads:[~2026-10-20 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 12:27 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-10-15 14:33 Mark Brown
2026-10-15 17:24 ` Miguel Ojeda
2026-08-11 15:15 Mark Brown
2026-08-11 16:22 ` Carlos Llamas
2026-08-11 17:02   ` Mark Brown
2026-08-12  7:30     ` 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=atdeNvRKFuQd2qHz@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=arnd@arndb.de \
    --cc=greg@kroah.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ojeda@kernel.org \
    /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®