Linux-Next discussions
 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>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Matt Roper" <matthew.d.roper@intel.com>,
	"Michal Wajdeczko" <michal.wajdeczko@intel.com>,
	"Raag Jadav" <raag.jadav@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: linux-next: manual merge of the driver-core tree with the drm-xe tree
Date: Sun, 26 Jul 2026 22:56:57 +0100	[thread overview]
Message-ID: <amaCqZUpvgKLe9gC@sirena.org.uk> (raw)

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

Hi all,

Today's linux-next merge of the driver-core tree got a conflict in:

  drivers/gpu/drm/xe/xe_i2c.c

between commits:

  5d8ed6b64220a ("drm/xe/i2c: Allow per domain unique id")
  9420abf8dbc2e ("drm/xe/i2c: Drop manual VF check")

from the drm-xe tree and commits:

  e766abbc5191b ("drm/xe/i2c: use platform_device_set_fwnode()")
  0f485f88656af ("drm/xe/i2c: use device_create_managed_software_node()")

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/gpu/drm/xe/xe_i2c.c
index a26c38bb17a15,5b0026bdb1c60..0000000000000
--- a/drivers/gpu/drm/xe/xe_i2c.c
+++ b/drivers/gpu/drm/xe/xe_i2c.c
@@@ -93,15 -93,7 +93,10 @@@ static int xe_i2c_register_adapter(stru
  {
  	struct pci_dev *pci = to_pci_dev(i2c->drm_dev);
  	struct platform_device *pdev;
- 	struct fwnode_handle *fwnode;
  	int ret;
 +	u32 id;
 +
- 	fwnode = fwnode_create_software_node(xe_i2c_adapter_properties, NULL);
- 	if (IS_ERR(fwnode))
- 		return PTR_ERR(fwnode);
- 
 +	id = (pci_domain_nr(pci->bus) << 16) | pci_dev_id(pci);
  
  	/*
  	 * Not using platform_device_register_full() here because we don't have
@@@ -109,11 -101,15 +104,15 @@@
  	 * uses that handle, but it may be called before
  	 * platform_device_register_full() is done.
  	 */
 -	pdev = platform_device_alloc(adapter_name, pci_dev_id(pci));
 +	pdev = platform_device_alloc(adapter_name, id);
- 	if (!pdev) {
- 		ret = -ENOMEM;
- 		goto err_fwnode_remove;
- 	}
+ 	if (!pdev)
+ 		return -ENOMEM;
+ 
+ 	ret = device_create_managed_software_node(&pdev->dev,
+ 						  xe_i2c_adapter_properties,
+ 						  NULL);
+ 	if (ret)
+ 		goto err_pdev_put;
  
  	if (i2c->adapter_irq) {
  		struct resource res;

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

             reply	other threads:[~2026-07-26 21:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-26 21:56 Mark Brown [this message]
2026-07-26 22:33 ` linux-next: manual merge of the driver-core tree with the drm-xe tree Danilo Krummrich

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=amaCqZUpvgKLe9gC@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=dakr@kernel.org \
    --cc=greg@kroah.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=matthew.d.roper@intel.com \
    --cc=michal.wajdeczko@intel.com \
    --cc=raag.jadav@intel.com \
    --cc=rafael@kernel.org \
    --cc=thomas.hellstrom@linux.intel.com \
    /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