From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Mark Brown <broonie@kernel.org>
Cc: 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 ieee1394 tree with the origin tree
Date: Tue, 20 Oct 2026 10:44:56 +0900 [thread overview]
Message-ID: <20261020014456.GA335452@sakamocchi.jp> (raw)
In-Reply-To: <atZBEI6G3PgKHKaW@sirena.co.uk>
Hi Mark,
Thank you for reporting the merge conflict.
The ieee1394 tree has now been rebased onto v7.3 tag to include a fix from
this PR[1]. This may have introduced a conflict in the linux-next tree.
I believe that linux-next will merge the v7.3 tag and merges all or
required branches onto it within a few days, at which point the conflict
should disappear. However, I'm not entirely familiar with how you maintain
the tree.
Please let me know if you encounter any further issues related to ieee1394
tree.
[1] [GIT PULL] firewire fixes for v7.3-final
https://lore.kernel.org/lkml/20261018103634.GA346762@sakamocchi.jp/
Thanks
Takashi Sakamoto
On Mon, Oct 19, 2026 at 05:10:56PM +0100, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the ieee1394 tree got a conflict in:
>
> drivers/firewire/core-transaction.c
>
> between commit:
>
> 7f9f2d6abc40f ("firewire: core: fix race condition in split transaction handling")
>
> from the origin tree and commit:
>
> 0f7228de31f1c ("firewire: core: expand close_transaction() into its callers and remove it")
>
> from the ieee1394 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.
prev parent reply other threads:[~2026-10-20 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 16:10 Mark Brown
2026-10-20 1:44 ` Takashi Sakamoto [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=20261020014456.GA335452@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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
all inboxes | Powered by JetHome®