From: Greg KH <greg@kroah.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Jahnavi MN <jahnavimn@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the char-misc tree with the char-misc.current tree
Date: Mon, 27 Jul 2026 14:18:15 +0200 [thread overview]
Message-ID: <2026072736-handclasp-bubbly-c879@gregkh> (raw)
In-Reply-To: <al8tlTE4KgeZ92PQ@google.com>
On Tue, Jul 21, 2026 at 08:28:05AM +0000, Alice Ryhl wrote:
> On Mon, Jul 20, 2026 at 03:44:42PM +0100, Mark Brown wrote:
> > Hi all,
> >
> > Today's linux-next merge of the char-misc tree got a conflict in:
> >
> > drivers/android/binder/thread.rs
> >
> > between commit:
> >
> > bb66b1a345253 ("rust_binder: only print failure if error has source")
> >
> > from the char-misc.current tree and commit:
> >
> > c61f3ad2213cf ("rust_binder: Implement BINDER_DEBUG_FAILED_TRANSACTION")
> >
> > 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 bc0ef8927905c,a51821dde0adf..0000000000000
> > --- a/drivers/android/binder/thread.rs
> > +++ b/drivers/android/binder/thread.rs
> > @@@ -1273,14 -1295,25 +1295,24 @@@ impl Thread
> > inner.extended_error =
> > ExtendedError::new(info.debug_id as u32, err.reply, source.to_errno());
> > }
> > - }
> >
> > - pr_warn!(
> > - "{}:{} transaction to {} failed: {err:?}",
> > - info.from_pid,
> > - info.from_tid,
> > - info.to_pid
> > - binder_debug!(
> > - FailedTransaction,
> > - "transaction {} to {}:{} failed {:?}, code {} size {}-{}",
> > - if info.is_reply {
> > - "reply"
> > - } else if info.is_oneway() {
> > - "async"
> > - } else {
> > - "call"
> > - },
> > - info.to_pid,
> > - info.to_tid,
> > - err,
> > - info.code,
> > - info.data_size,
> > - info.offsets_size
> > - );
> > ++ binder_debug!(
> > ++ FailedTransaction,
> > ++ "transaction {} to {}:{} failed {:?}, code {} size {}-{}",
> > ++ if info.is_reply {
> > ++ "reply"
> > ++ } else if info.is_oneway() {
> > ++ "async"
> > ++ } else {
> > ++ "call"
> > ++ },
> > ++ info.to_pid,
> > ++ info.to_tid,
> > ++ err,
> > ++ info.code,
> > ++ info.data_size,
> > ++ info.offsets_size
> > + );
> > - }
> > }
> > }
>
> I think you're missing a closing } after the binder_debug! call.
> Otherwise LGTM.
>
> error: this file contains an unclosed delimiter
> --> drivers/android/binder/thread.rs:1743:3
> |
> 453 | impl Thread {
> | - unclosed delimiter
> ...
> 1290 | if let Some(source) = &err.source {
> | - this delimiter might not be properly closed...
> ...
> 1316 | }
> | - ...as it matches this but it has different indentation
> ...
> 1743 | }
> | ^
>
> error: aborting due to 1 previous error
That trailing ) on the same indent line just looks odd to me, which is
why I can see it's going to be easy to make this type of merge
mistake...
I've done this now in my tree so all should be good going forward,
thanks!
greg k-h
next prev parent reply other threads:[~2026-07-27 12:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 14:44 linux-next: manual merge of the char-misc tree with the char-misc.current tree Mark Brown
2026-07-21 8:28 ` Alice Ryhl
2026-07-27 12:18 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-20 14:46 Mark Brown
2026-07-27 12:18 ` Greg KH
2026-05-25 15:07 Mark Brown
2025-11-14 3:32 Stephen Rothwell
2025-11-14 19:10 ` Dinh Nguyen
2025-10-24 1:49 Stephen Rothwell
2025-10-24 5:24 ` Greg KH
2021-12-06 3:49 Stephen Rothwell
2021-12-06 13:43 ` Andy Shevchenko
2021-12-06 16:17 ` Ralph Siemsen
2021-12-06 16:44 ` Andy Shevchenko
2021-12-13 9:18 ` Greg KH
2022-01-07 23:18 ` Kees Cook
2019-10-18 3:26 Stephen Rothwell
2019-10-18 10:06 ` Greg KH
2019-04-03 3:56 Stephen Rothwell
2019-04-03 5:06 ` Srinivas Kandagatla
2019-04-03 6:39 ` Bo YU
2018-12-04 4:35 Stephen Rothwell
2018-12-04 7:42 ` Greg KH
2018-12-04 8:46 ` Dexuan Cui
2018-12-10 9:47 ` Greg KH
2018-12-10 18:51 ` Dexuan Cui
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=2026072736-handclasp-bubbly-c879@gregkh \
--to=greg@kroah.com \
--cc=aliceryhl@google.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=jahnavimn@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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