From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
linux-kernel@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Zhu Lingshan <lingshan.zhu@intel.com>
Subject: Re: [PATCH fyi 1/1] perf trace beauty: Sync linux/vhost.h with the kernel sources
Date: Tue, 2 Apr 2024 18:39:12 -0300 [thread overview]
Message-ID: <Zgx7APFHoWQgVEDw@x1> (raw)
In-Reply-To: <CAM9d7cjSN6M4VvKRifwQ=bpvbc92pLoghnjCwWiOE7SFSzXWRg@mail.gmail.com>
On Tue, Apr 02, 2024 at 02:04:39PM -0700, Namhyung Kim wrote:
> On Thu, Mar 21, 2024 at 1:41 PM Arnaldo Carvalho de Melo
> <acme@kernel.org> wrote:
> >
> > tldr; Just FYI, I'm carrying this on the perf tools tree.
>
> Have you applied this to perf-tools-next?
Nope.
> > +++ after 2024-03-21 17:34:07.687563333 -0300
> > @@ -49,6 +49,7 @@
> > [0x7B] = "VDPA_GET_VRING_GROUP",
> > [0x7F] = "VDPA_GET_VRING_DESC_GROUP",
> > [0x80] = "VDPA_GET_VQS_COUNT",
> > + [0x80] = "VDPA_GET_VRING_SIZE",
>
> This gives me a build error:
I noticed it and removed it.
⬢[acme@toolbox perf-tools-next]$ git log --oneline perf-tools-next/perf-tools-next torvalds/master.. | grep vhost
4962e1949608fed9 perf beauty: Move uapi/linux/vhost.h copy out of the directory used to build perf
⬢[acme@toolbox perf-tools-next]$
Thanks for double checking!
- Arnaldo
next prev parent reply other threads:[~2024-04-02 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 20:41 [PATCH fyi 1/1] perf trace beauty: Sync linux/vhost.h with the kernel sources Arnaldo Carvalho de Melo
2024-04-02 21:04 ` Namhyung Kim
2024-04-02 21:15 ` Michael S. Tsirkin
2024-04-02 21:39 ` Arnaldo Carvalho de Melo [this message]
2024-04-02 21:23 ` 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=Zgx7APFHoWQgVEDw@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=namhyung@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