From: Greg KH <greg@kroah.com>
To: Mark Brown <broonie@kernel.org>
Cc: Atharva Tiwari <atharvatiwarilinuxdev@gmail.com>,
Daniel Gomez <da.gomez@samsung.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Petr Pavlu <petr.pavlu@suse.com>,
Sami Tolvanen <samitolvanen@google.com>
Subject: Re: linux-next: manual merge of the usb tree with the modules tree
Date: Wed, 14 Oct 2026 17:48:20 +0200 [thread overview]
Message-ID: <2026101414-remodeler-hypnosis-0620@gregkh> (raw)
In-Reply-To: <as-ZUTCmpY2iZf_T@sirena.org.uk>
On Wed, Oct 14, 2026 at 04:01:37PM +0100, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the usb tree got a conflict in:
>
> drivers/thunderbolt/tb.c
>
> between commit:
>
> 08abfa5a161e1 ("drivers: Replace __MODULE_STRING() with __stringify()")
>
> from the modules tree and commit:
>
> 41d5a1fc28100 ("thunderbolt: Move tb_apple_add_links() to pci.c")
>
> from the usb 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/thunderbolt/tb.c
> index 9537110a5aa8b,4da608ccbccbf..0000000000000
> --- a/drivers/thunderbolt/tb.c
> +++ b/drivers/thunderbolt/tb.c
> @@@ -10,8 -10,6 +10,7 @@@
> #include <linux/errno.h>
> #include <linux/delay.h>
> #include <linux/pm_runtime.h>
> - #include <linux/platform_data/x86/apple.h>
> +#include <linux/stringify.h>
>
> #include "tb.h"
> #include "tb_regs.h"
Looks good to me, thanks!
greg k-h
prev parent reply other threads:[~2026-10-14 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 15:01 linux-next: manual merge of the usb tree with the modules tree Mark Brown
2026-10-14 15:48 ` Greg KH [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=2026101414-remodeler-hypnosis-0620@gregkh \
--to=greg@kroah.com \
--cc=atharvatiwarilinuxdev@gmail.com \
--cc=broonie@kernel.org \
--cc=da.gomez@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.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