All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Yang Jihong <yangjihong1@huawei.com>,
	peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
	alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	irogers@google.com, linux-perf-users@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf help: Use HAVE_LIBTRACEEVENT to filter out unsupported commands
Date: Mon, 2 Jan 2023 11:52:25 -0300	[thread overview]
Message-ID: <Y7LvqfynJ9oxeyjt@kernel.org> (raw)
In-Reply-To: <CAM9d7cjoFCqEBVwA+_D5ZNOnVcUo1Y6fysZmG0-uvqm9kUBJGA@mail.gmail.com>

Em Tue, Dec 27, 2022 at 11:34:46AM -0800, Namhyung Kim escreveu:
> Hello,
> 
> On Mon, Dec 26, 2022 at 1:00 AM Yang Jihong <yangjihong1@huawei.com> wrote:
> >
> > Commands such as kmem, kwork, lock, sched, trace and timechart depend on
> > libtraceevent, these commands need to be isolated using HAVE_LIBTRACEEVENT
> > macro when cmdlist generation.
> >
> > The output of the generate-cmdlist.sh script is as follows:
> >
> >   # ./util/generate-cmdlist.sh
> >   /* Automatically generated by ./util/generate-cmdlist.sh */
> >   struct cmdname_help
> >   {
> >       char name[16];
> >       char help[80];
> >   };

Thanks, applied.

- Arnaldo


      reply	other threads:[~2023-01-02 14:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26  8:57 [PATCH] perf help: Use HAVE_LIBTRACEEVENT to filter out unsupported commands Yang Jihong
2022-12-27 19:34 ` Namhyung Kim
2023-01-02 14:52   ` Arnaldo Carvalho de Melo [this message]

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=Y7LvqfynJ9oxeyjt@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=yangjihong1@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.