From: Miguel Ojeda <ojeda@kernel.org>
To: gregkh@linuxfoundation.org
Cc: akpm@linux-foundation.org, arnd@arndb.de,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [GIT PULL] Char/Misc/IIO driver driver updates for 7.3-rc1
Date: Tue, 25 Aug 2026 22:05:16 +0200 [thread overview]
Message-ID: <20260825200516.42078-1-ojeda@kernel.org> (raw)
In-Reply-To: <2026082525-spoils-gutless-f1ff@gregkh>
On Tue, 25 Aug 2026 13:15:35 +0200 Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Tue, Aug 25, 2026 at 01:14:22PM +0200, Greg KH wrote:
> >
> > All of these have been in linux-next for a while, with the only reported
> > issues being some major merge conflicts. Miguel pointed out some of
> > these with the Rust tree merge, which is the majority of them. I'll
> > follow up with a diffstat of the merge resolution I made against your
> > most recent tree, which works for me.
>
> And here below is my merge resolution. Watchout for the
> drivers/android/binder/netlink.rs fixup that is needed to get things to
> build properly. It's not a merge conflict, but still is required due to
> the module ownership changes coming from the rust tree.
Looks good to me -- I did it on my side and I also checked that it
matches what we have in linux-next.
The only difference is that here:
+ LockClassKey, //
+ }, //
+ types::Opaque, //
we can already remove the `//` in the middle, i.e.
+ LockClassKey, //
+ },
+ types::Opaque, //
Thanks!
Cheers,
Miguel
next prev parent reply other threads:[~2026-08-25 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 11:14 [GIT PULL] Char/Misc/IIO driver driver updates for 7.3-rc1 Greg KH
2026-08-25 11:15 ` Greg KH
2026-08-25 20:05 ` Miguel Ojeda [this message]
2026-08-25 20:11 ` Miguel Ojeda
2026-08-25 19:51 ` pr-tracker-bot
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=20260825200516.42078-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.