From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Michael S. Tsirkin" <mst@redhat.com>,
David Miller <davem@davemloft.net>
Cc: Networking <netdev@vger.kernel.org>,
Laurent Vivier <lvivier@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the vhost tree
Date: Fri, 3 Feb 2023 13:33:03 +1100 [thread overview]
Message-ID: <20230203133303.5cf19f41@canb.auug.org.au> (raw)
In-Reply-To: <20230203132629.30cf161c@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
Hi all,
On Fri, 3 Feb 2023 13:26:29 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> The following commits are also in Linus Torvalds' tree as different
^^^^^^^^^^^^^^^
Actually not in Linus' tree, just the net-next tree (semi-automation
sometimes fails :-)).
> commits (but the same patches):
>
> 022659ee3363 ("virtio_net: notify MAC address change on device initialization")
> d0aa1f8e8d63 ("virtio_net: disable VIRTIO_NET_F_STANDBY if VIRTIO_NET_F_MAC is not set")
>
> These are commits
>
> 9f62d221a4b0 ("virtio_net: notify MAC address change on device initialization")
> 7c06458c102e ("virtio_net: disable VIRTIO_NET_F_STANDBY if VIRTIO_NET_F_MAC is not set")
>
> in the net-next tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-02-03 2:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 2:26 linux-next: duplicate patches in the vhost tree Stephen Rothwell
2023-02-03 2:33 ` Stephen Rothwell [this message]
2023-02-03 9:34 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2024-04-23 5:33 Stephen Rothwell
2025-01-09 3:40 Stephen Rothwell
2025-01-09 5:23 ` Andrew Morton
2025-01-09 7:45 ` Michael S. Tsirkin
2025-01-10 0:48 ` Andrew Morton
2025-05-29 22:17 Stephen Rothwell
2025-10-19 20:54 Stephen Rothwell
2025-11-16 19:54 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=20230203133303.5cf19f41@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@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