From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christian Brauner <brauner@kernel.org>,
Alice Ryhl <aliceryhl@google.com>,
Danilo Krummrich <dakr@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Remo Senekowitsch <remo@buenzli.dev>
Subject: Re: linux-next: manual merge of the driver-core tree with the vfs-brauner tree
Date: Tue, 24 Jun 2025 08:24:47 +0100 [thread overview]
Message-ID: <2025062437-composite-jaws-2bbf@gregkh> (raw)
In-Reply-To: <20250624144231.3598eb5e@canb.auug.org.au>
On Tue, Jun 24, 2025 at 02:42:31PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the driver-core tree got a conflict in:
>
> rust/helpers/helpers.c
>
> between commit:
>
> 6efbf978891b ("poll: rust: allow poll_table ptrs to be null")
>
> from the vfs-brauner tree and commit:
>
> a2801affa710 ("rust: device: Create FwNode abstraction for accessing device properties")
>
> from the driver-core 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 d2887e3b2826,393ad201befb..000000000000
> --- a/rust/helpers/helpers.c
> +++ b/rust/helpers/helpers.c
> @@@ -32,7 -32,7 +32,8 @@@
> #include "platform.c"
> #include "pci.c"
> #include "pid_namespace.c"
> +#include "poll.c"
> + #include "property.c"
> #include "rbtree.c"
> #include "rcu.c"
> #include "refcount.c"
Looks good, thanks!
prev parent reply other threads:[~2025-06-24 7:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 4:42 linux-next: manual merge of the driver-core tree with the vfs-brauner tree Stephen Rothwell
2025-06-24 7:24 ` Greg KH [this message]
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=2025062437-composite-jaws-2bbf@gregkh \
--to=greg@kroah.com \
--cc=aliceryhl@google.com \
--cc=brauner@kernel.org \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=remo@buenzli.dev \
--cc=sfr@canb.auug.org.au \
/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