Linux-Next discussions
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Mark Brown <broonie@kernel.org>
Cc: Greg KH <greg@kroah.com>, Danilo Krummrich <dakr@kernel.org>,
	 "Rafael J. Wysocki" <rafael@kernel.org>,
	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>
Subject: Re: linux-next: manual merge of the driver-core tree with the origin tree
Date: Mon, 13 Jul 2026 17:15:34 +0200	[thread overview]
Message-ID: <alUA3L41eEuKNI2o@monoceros> (raw)
In-Reply-To: <alTxJTV0crJ8DNar@sirena.org.uk>

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

Hello,

On Mon, Jul 13, 2026 at 03:07:33PM +0100, Mark Brown wrote:
> Hi all,
> 
> Today's linux-next merge of the driver-core tree got a conflict in:
> 
>   include/linux/platform_device.h
> 
> between commit:
> 
>   00cd8fc630e06 ("driver core: platform: Include header for struct platform_device_id")
> 
> from the origin tree and commits:
> 
>   714cfe9e143fe ("driver core: platform: provide platform_device_set_of_node()")
>   8877c06885ce4 ("driver core: platform: provide platform_device_set_fwnode()")
> 
> 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 include/linux/platform_device.h
> index 8c566f09d04ef,94b8d2b46e913..0000000000000
> --- a/include/linux/platform_device.h
> +++ b/include/linux/platform_device.h
> @@@ -19,6 -18,9 +19,8 @@@
>   struct irq_affinity;
>   struct mfd_cell;
>   struct property_entry;
>  -struct platform_device_id;
> + struct device_node;
> + struct fwnode_handle;
>   
>   struct platform_device {
>   	const char	*name;

That looks right, thank you

Best regards
Uwe


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

      reply	other threads:[~2026-07-13 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 14:07 linux-next: manual merge of the driver-core tree with the origin tree Mark Brown
2026-07-13 15:15 ` Uwe Kleine-König [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=alUA3L41eEuKNI2o@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=broonie@kernel.org \
    --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=rafael@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