From: Greg KH <greg@kroah.com>
To: Mark Brown <broonie@kernel.org>
Cc: Danilo Krummrich <dakr@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Rob Herring <robh@kernel.org>
Subject: Re: linux-next: manual merge of the driver-core tree with the devicetree tree
Date: Wed, 18 Mar 2026 08:37:15 +0100 [thread overview]
Message-ID: <2026031803-chirping-promotion-4c3a@gregkh> (raw)
In-Reply-To: <abl_FcMjGGAf1YHt@sirena.org.uk>
On Tue, Mar 17, 2026 at 04:19:33PM +0000, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the driver-core tree got a conflict in:
>
> drivers/of/base.c
>
> between commit:
>
> 82b6c1b542ea0 ("of: Add of_machine_get_match() helper")
>
> from the devicetree tree and commits:
>
> 59621105ffca7 ("of: provide of_machine_read_compatible()")
> c86d3b7b847cc ("of: provide of_machine_read_model()")
>
> 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.
Fix looks good, thanks!
greg k-h
next prev parent reply other threads:[~2026-03-18 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 16:19 linux-next: manual merge of the driver-core tree with the devicetree tree Mark Brown
2026-03-18 7:37 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-06 8:19 Stephen Rothwell
2021-04-06 9:11 ` Greg KH
2021-04-06 16:19 ` Saravana Kannan
2020-07-06 3:23 Stephen Rothwell
2013-06-17 5:33 Stephen Rothwell
2013-06-17 19:58 ` Greg KH
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=2026031803-chirping-promotion-4c3a@gregkh \
--to=greg@kroah.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh@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