From: Jens Axboe <axboe@kernel.dk>
To: Mark Brown <broonie@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
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 block tree with the origin tree
Date: Tue, 16 Jun 2026 08:04:50 -0600 [thread overview]
Message-ID: <d968a9de-df62-4120-bc95-21483a15785a@kernel.dk> (raw)
In-Reply-To: <ajFXBeLQC96YuC0p@sirena.org.uk>
On 6/16/26 8:00 AM, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the block tree got a conflict in:
>
> io_uring/net.c
>
> between commit:
>
> 9b40ba14edcdf ("Merge tag 'for-7.2/io_uring-20260615' of git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux")
>
> from the origin tree and commit:
>
> c59e546eda5aa ("Merge branch 'for-7.2/io_uring' into for-next")
>
> from the block 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.
I updated my for-next a few hours ago, I think you're using an older
one. Regardless, it's fine.
--
Jens Axboe
next prev parent reply other threads:[~2026-06-16 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 14:00 linux-next: manual merge of the block tree with the origin tree Mark Brown
2026-06-16 14:04 ` Jens Axboe [this message]
2026-06-16 14:10 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2023-04-19 14:39 broonie
2020-12-14 4:01 Stephen Rothwell
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=d968a9de-df62-4120-bc95-21483a15785a@kernel.dk \
--to=axboe@kernel.dk \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=torvalds@linux-foundation.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