From: Mark Brown <broonie@kernel•org>
To: "Michael S. Tsirkin" <mst@redhat•com>
Cc: Jakub Kicinski <kuba@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: manual merge of the vhost tree with the net-next tree
Date: Mon, 29 Sep 2025 15:40:28 +0100 [thread overview]
Message-ID: <aNqaXDjhCkEwpKIw@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
Hi all,
Today's linux-next merge of the vhost tree got a conflict in:
include/linux/ptr_ring.h
between commit:
4e9510f162188 ("ptr_ring: drop duplicated tail zeroing code")
from the net-next tree and commits:
4a37c69fc60bf ("ptr_ring: drop duplicated tail zeroing code")
from the vhost 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 include/linux/ptr_ring.h
index a736b16859a6c,ba90c0e6ce703..0000000000000
--- a/include/linux/ptr_ring.h
+++ b/include/linux/ptr_ring.h
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-09-29 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 14:40 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-17 6:15 linux-next: manual merge of the vhost tree with the net-next tree Stephen Rothwell
2024-07-09 7:05 Stephen Rothwell
2023-08-15 8:01 Stephen Rothwell
2023-06-23 3:04 Stephen Rothwell
2023-07-11 1:01 ` Stephen Rothwell
2019-04-03 4:22 Stephen Rothwell
2016-06-16 4:19 Stephen Rothwell
2013-04-29 7:29 Stephen Rothwell
2012-04-19 5:35 Stephen Rothwell
2012-04-19 5:40 ` Michael S. Tsirkin
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=aNqaXDjhCkEwpKIw@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mst@redhat$(echo .)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