public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Greg KH <greg@kroah.com>, Danilo Krummrich <dakr@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Rob Herring <robh@kernel.org>
Subject: linux-next: manual merge of the driver-core tree with the devicetree tree
Date: Tue, 17 Mar 2026 16:19:33 +0000	[thread overview]
Message-ID: <abl_FcMjGGAf1YHt@sirena.org.uk> (raw)

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

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.

diff --cc drivers/of/base.c
index af048ab88e694,bf4a51887d742..0000000000000
--- a/drivers/of/base.c
+++ b/drivers/of/base.c
@@@ -434,13 -434,42 +434,41 @@@ bool of_machine_compatible_match(const 
  }
  EXPORT_SYMBOL(of_machine_compatible_match);
  
+ /**
+  * of_machine_read_compatible - Get the compatible string of this machine
+  * @compatible: address at which the address of the compatible string will be
+  *              stored
+  * @index: index of the compatible entry in the list
+  *
+  * Returns:
+  * 0 on success, negative error number on failure.
+  */
+ int of_machine_read_compatible(const char **compatible, unsigned int index)
+ {
+ 	return of_property_read_string_index(of_root, "compatible", index, compatible);
+ }
+ EXPORT_SYMBOL_GPL(of_machine_read_compatible);
+ 
+ /**
+  * of_machine_read_model - Get the model string of this machine
+  * @model: address at which the address of the model string will be stored
+  *
+  * Returns:
+  * 0 on success, negative error number on failure.
+  */
+ int of_machine_read_model(const char **model)
+ {
+ 	return of_property_read_string(of_root, "model", model);
+ }
+ EXPORT_SYMBOL_GPL(of_machine_read_model);
+ 
  /**
 - * of_machine_device_match - Test root of device tree against a of_device_id array
 + * of_machine_get_match - Test root of device tree against an of_device_id array
   * @matches:	NULL terminated array of of_device_id match structures to search in
   *
 - * Returns true if the root node has any of the given compatible values in its
 - * compatible property.
 + * Returns matched entry or NULL
   */
 -bool of_machine_device_match(const struct of_device_id *matches)
 +const struct of_device_id *of_machine_get_match(const struct of_device_id *matches)
  {
  	struct device_node *root;
  	const struct of_device_id *match = NULL;

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

             reply	other threads:[~2026-03-17 16:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 16:19 Mark Brown [this message]
2026-03-18  7:37 ` linux-next: manual merge of the driver-core tree with the devicetree tree Greg KH
  -- 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=abl_FcMjGGAf1YHt@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=dakr@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=greg@kroah.com \
    --cc=gregkh@linuxfoundation.org \
    --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