Linux-Next discussions
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Mark Brown <broonie@kernel.org>,
	 Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 Linux Next Mailing List <linux-next@vger.kernel.org>,
	Viacheslav Bocharov <v@baodeep.com>
Subject: Re: linux-next: manual merge of the device-id tree with the gpio tree
Date: Wed, 1 Jul 2026 16:58:17 +0200	[thread overview]
Message-ID: <akUqc1sq7BBoazki@monoceros> (raw)
In-Reply-To: <akUlscmgGk8TLzgN@sirena.org.uk>

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

Hello Mark, hello Bartosz,

On Wed, Jul 01, 2026 at 03:35:29PM +0100, Mark Brown wrote:
> Today's linux-next merge of the device-id tree got a conflict in:
> 
>   drivers/gpio/gpio-shared-proxy.c
> 
> between commit:
> 
>   163ba8782d521 ("Replace <linux/mod_devicetable.h> by more specific <linux/device-id/*.h> (c files)")
> 
> from the device-id tree and commit:
> 
>   efecde8a254d1 ("gpio: shared-proxy: always serialize with a sleeping mutex")
> 
> from the device-id 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/gpio/gpio-shared-proxy.c
> index 10ca2ef77ef34,d3625b8d0ced2..0000000000000
> --- a/drivers/gpio/gpio-shared-proxy.c
> +++ b/drivers/gpio/gpio-shared-proxy.c
> @@@ -9,10 -9,7 +9,9 @@@
>   #include <linux/err.h>
>   #include <linux/gpio/consumer.h>
>   #include <linux/gpio/driver.h>
>  +#include <linux/lockdep.h>
> - #include <linux/mod_devicetable.h>
>   #include <linux/module.h>
>  +#include <linux/mutex.h>
>   #include <linux/string_choices.h>
>   #include <linux/types.h>

thanks to Mark for the notification, the merge resolution looks right.

Bartosz, I intend to send the changes that are currently in the
device-id branch to Linus for 7.2-rc2. So it's probably on you to notify
Linus about the merge conflict. (Or you rebase on 7.2-rc2 until then.)

Best regards
Uwe

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

      reply	other threads:[~2026-07-01 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 14:35 linux-next: manual merge of the device-id tree with the gpio tree Mark Brown
2026-07-01 14:58 ` 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=akUqc1sq7BBoazki@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=v@baodeep.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