From: Mark Brown <broonie@kernel•org>
To: Mika Westerberg <mika.westerberg@linux•intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Michael Bommarito <michael.bommarito@gmail•com>
Subject: linux-next: manual merge of the thunderbolt tree with the thunderbolt-fixes tree
Date: Wed, 20 May 2026 13:18:32 +0100 [thread overview]
Message-ID: <ag2mmKbGy_hyoc8V@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
Hi all,
Today's linux-next merge of the thunderbolt tree got a conflict in:
drivers/thunderbolt/property.c
between commit:
928abe19fbf01 ("thunderbolt: property: Cap recursion depth in __tb_property_parse_dir()")
from the thunderbolt-fixes tree and commit:
7e6445d9d6f7d ("thunderbolt: Add tb_property_merge_dir()")
from the thunderbolt 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/property.c
index da2c59a17db5c,6b9666b611818..0000000000000
--- a/drivers/thunderbolt/property.c
+++ b/drivers/thunderbolt/property.c
@@@ -39,7 -37,8 +39,8 @@@ struct tb_property_dir_entry
static struct tb_property_dir *__tb_property_parse_dir(const u32 *block,
size_t block_len, unsigned int dir_offset, size_t dir_len,
- bool is_root);
+ bool is_root, unsigned int depth);
+ static struct tb_property *tb_property_copy(const struct tb_property *property);
static inline void parse_dwdata(void *dst, const void *src, size_t dwords)
{
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2026-05-20 12:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ag2mmKbGy_hyoc8V@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=michael.bommarito@gmail$(echo .)com \
--cc=mika.westerberg@linux$(echo .)intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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