Linux-Next discussions
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Miao Li" <limiao@kylinos.cn>,
	"Uwe Kleine-König" <ukleinek@kernel.org>
Subject: Re: linux-next: manual merge of the device-id tree with the iio tree
Date: Thu, 2 Jul 2026 19:39:56 +0100	[thread overview]
Message-ID: <20260702193956.614504d1@jic23-huawei> (raw)
In-Reply-To: <akajRDPG1mkYFL9K@sirena.org.uk>

On Thu, 2 Jul 2026 18:43:32 +0100
Mark Brown <broonie@kernel.org> wrote:

> Hi all,
> 
> Today's linux-next merge of the device-id tree got a conflict in:
> 
>   drivers/iio/accel/stk8ba50.c
> 
> between commit:
> 
>   e8de771d80a3a ("iio: accel: stk8ba50: Update includes to match IWYU")
> 
> from the iio tree and commit:
> 
>   80f98bb4f07ea ("Replace <linux/mod_devicetable.h> by more specific <linux/device-id/*.h> (c files)")
> 
> 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.

Thanks.  That header drop patch is likely to cause quite a lot of context
and minor merge conflicts. I guess that'll resolve if anyone affected
merges in rc2 once available.

Jonathan

> 
> diff --cc drivers/iio/accel/stk8ba50.c
> index 4bacc007897ae,d0c53b8ac850a..0000000000000
> --- a/drivers/iio/accel/stk8ba50.c
> +++ b/drivers/iio/accel/stk8ba50.c
> @@@ -7,19 -7,11 +7,18 @@@
>    * STK8BA50 7-bit I2C address: 0x18.
>    */
>   
>  +#include <linux/array_size.h>
>  +#include <linux/bitops.h>
>  +#include <linux/dev_printk.h>
>  +#include <linux/errno.h>
>   #include <linux/i2c.h>
>   #include <linux/interrupt.h>
>  -#include <linux/kernel.h>
>   #include <linux/module.h>
> - #include <linux/mod_devicetable.h>
>  +#include <linux/mutex.h>
>  +#include <linux/pm.h>
>  +#include <linux/sysfs.h>
>   #include <linux/types.h>
>  +
>   #include <linux/iio/buffer.h>
>   #include <linux/iio/iio.h>
>   #include <linux/iio/sysfs.h>


      reply	other threads:[~2026-07-02 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 17:43 linux-next: manual merge of the device-id tree with the iio tree Mark Brown
2026-07-02 18:39 ` Jonathan Cameron [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=20260702193956.614504d1@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=broonie@kernel.org \
    --cc=limiao@kylinos.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=u.kleine-koenig@baylibre.com \
    --cc=ukleinek@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