linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Paolo Abeni" <pabeni@redhat.com>,
	netdev@vger.kernel.org,
	"Willem de Bruijn" <willemdebruijn.kernel@gmail.com>,
	"Jason Wang" <jasowang@redhat.com>,
	"Andrew Lunn" <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
	"Eugenio Pérez" <eperezma@redhat.com>,
	"Yuri Benditovich" <yuri.benditovich@daynix.com>,
	"Akihiko Odaki" <akihiko.odaki@daynix.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	kvm@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v7 net-next 0/9] virtio: introduce GSO over UDP tunnel
Date: Tue, 8 Jul 2025 08:24:04 -0700	[thread overview]
Message-ID: <20250708082404.21d1fe61@kernel.org> (raw)
In-Reply-To: <20250708105816-mutt-send-email-mst@kernel.org>

On Tue, 8 Jul 2025 11:01:30 -0400 Michael S. Tsirkin wrote:
> > git@github.com:pabeni/linux-devel.git virtio_udp_tunnel_07_07_2025
> > 
> > The first 5 patches in this series, that is, the virtio features
> > extension bits are also available at [2]:
> > 
> > git@github.com:pabeni/linux-devel.git virtio_features_extension_07_07_2025
> > 
> > Ideally the virtio features extension bit should go via the virtio tree
> > and the virtio_net/tun patches via the net-next tree. The latter have
> > a dependency in the first and will cause conflicts if merged via the
> > virtio tree, both when applied and at merge window time - inside Linus
> > tree.
> > 
> > To avoid such conflicts and duplicate commits I think the net-next
> > could pull from [1], while the virtio tree could pull from [2].  
> 
> Or I could just merge all of this in my tree, if that's ok
> with others?

No strong preference here. My first choice would be a branch based
on v6.16-rc5 so we can all pull in and resolve the conflicts that
already exist. But I haven't looked how bad the conflicts would 
be for virtio if we did that. On net-next side they look manageable.

  reply	other threads:[~2025-07-08 15:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08  7:08 [PATCH v7 net-next 0/9] virtio: introduce GSO over UDP tunnel Paolo Abeni
2025-07-08  7:08 ` [PATCH v7 net-next 1/9] scripts/kernel_doc.py: properly handle VIRTIO_DECLARE_FEATURES Paolo Abeni
2025-07-08  7:08 ` [PATCH v7 net-next 2/9] virtio: introduce extended features Paolo Abeni
2025-07-08  7:08 ` [PATCH v7 net-next 3/9] virtio_pci_modern: allow configuring " Paolo Abeni
2025-07-08  7:09 ` [PATCH v7 net-next 4/9] vhost-net: " Paolo Abeni
2025-07-08  7:09 ` [PATCH v7 net-next 5/9] virtio_net: add supports for extended offloads Paolo Abeni
2025-07-08  7:09 ` [PATCH v7 net-next 6/9] net: implement virtio helpers to handle UDP GSO tunneling Paolo Abeni
2025-07-08  7:09 ` [PATCH v7 net-next 7/9] virtio_net: enable gso over UDP tunnel support Paolo Abeni
2025-07-08  7:09 ` [PATCH v7 net-next 8/9] tun: " Paolo Abeni
2025-07-08  7:09 ` [PATCH v7 net-next 9/9] vhost/net: " Paolo Abeni
2025-07-08 15:01 ` [PATCH v7 net-next 0/9] virtio: introduce GSO over UDP tunnel Michael S. Tsirkin
2025-07-08 15:24   ` Jakub Kicinski [this message]
2025-07-08 16:00     ` Michael S. Tsirkin
2025-07-08 16:43       ` Paolo Abeni
2025-07-08 17:00         ` Paolo Abeni
2025-07-08 19:50           ` Michael S. Tsirkin
2025-07-08 18:23         ` Michael S. Tsirkin
2025-07-09  9:02           ` Paolo Abeni
2025-07-10 20:50 ` patchwork-bot+netdevbpf

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=20250708082404.21d1fe61@kernel.org \
    --to=kuba@kernel.org \
    --cc=akihiko.odaki@daynix.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemdebruijn.kernel@gmail.com \
    --cc=xuanzhuo@linux.alibaba.com \
    --cc=yuri.benditovich@daynix.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;
as well as URLs for NNTP newsgroup(s).