linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the vhost tree
Date: Wed, 27 Aug 2025 10:26:16 -0700	[thread overview]
Message-ID: <aK8_uOoLxLOniEbR@google.com> (raw)
In-Reply-To: <20250827062218-mutt-send-email-mst@kernel.org>

Hello,

On Wed, Aug 27, 2025 at 06:23:52AM -0400, Michael S. Tsirkin wrote:
> On Wed, Aug 27, 2025 at 12:46:54PM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > The following commit is also in the perf-current tree as a different
> > commit (but the same patch):
> > 
> >   c67e16d30dca ("tools headers: Sync uapi/linux/vhost.h with the kernel source"
> > )
> > 
> > This is commit
> > 
> >   f79a62f4b3c7 ("tools headers: Sync uapi/linux/vhost.h with the kernel source")
> > 
> > in the perf-current tree.
> 
> 
> Hmm.  I could drop mine I guess, but it only really makes sense after:
> 
>     vhost: Fix ioctl # for VHOST_[GS]ET_FORK_FROM_OWNER
>     
> 
> which is not in the perf tree.

Yep, so I was waiting for you to send PR with the fix.
It seems you already removed the commit in your tree.
I'll send a PR for perf tools with this change.

Thanks,
Namhyung


  reply	other threads:[~2025-08-27 17:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-27  2:46 linux-next: duplicate patch in the vhost tree Stephen Rothwell
2025-08-27 10:23 ` Michael S. Tsirkin
2025-08-27 17:26   ` Namhyung Kim [this message]
2025-08-27 22:04     ` Michael S. Tsirkin
2025-08-27 23:50       ` Namhyung Kim
  -- strict thread matches above, loose matches on Subject: below --
2024-10-24  4:15 Stephen Rothwell
2024-09-11  7:47 Stephen Rothwell
2024-09-11 10:41 ` Michael S. Tsirkin
2024-07-18  5:01 Stephen Rothwell
2024-07-18  5:16 ` Greg KH
2024-05-14  6:18 Stephen Rothwell
2024-02-23  3:25 Stephen Rothwell
2024-01-05  4:06 Stephen Rothwell
2023-06-05  2:24 Stephen Rothwell
2023-04-11  5:19 Stephen Rothwell
2023-04-11 22:18 ` Jonathan Corbet
2023-04-12  2:51   ` 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=aK8_uOoLxLOniEbR@google.com \
    --to=namhyung@kernel.org \
    --cc=arnaldo.melo@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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).