All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Guilherme Amadio <amadio@gentoo.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ian Rogers <irogers@google.com>,
	Thorsten Leemhuis <linux@leemhuis.info>,
	Leo Yan <leo.yan@arm.com>,
	linux-perf-users@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/6] tools: Make pkg-config dependency checks usable by other tools
Date: Wed, 3 Jul 2024 14:33:21 -0700	[thread overview]
Message-ID: <ZoXDoajJqDiIcgwg@google.com> (raw)
In-Reply-To: <20240703153617.650fcc1c@rorschach.local.home>

On Wed, Jul 03, 2024 at 03:36:17PM -0400, Steven Rostedt wrote:
> On Tue, 2 Jul 2024 16:40:46 -0700
> Namhyung Kim <namhyung@kernel.org> wrote:
> 
> > +CC Steve and linux-trace-kernel list.
> 
> There doesn't seem to be a cover page, and it doesn't apply on
> v6.10-rc6 nor on tip.

Oh, sorry.  You can find the whole series here.

https://lore.kernel.org/linux-perf-users/20240628203432.3273625-1-amadio@gentoo.org/#r

I think this is based on the perf-tools-next tree and depends on perf
changes.  If you're ok with the change, I can carry it in the perf tree.

Thanks,
Namhyung


  reply	other threads:[~2024-07-03 21:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240628202608.3273329-1-amadio@gentoo.org>
2024-06-28 20:34 ` [PATCH v2 1/6] perf build: Conditionally add feature check flags for libtrace{event,fs} Guilherme Amadio
2024-06-28 20:34   ` [PATCH v2 2/6] perf build: Warn if libtracefs is not found Guilherme Amadio
2024-06-28 20:34   ` [PATCH v2 3/6] tools: Make pkg-config dependency checks usable by other tools Guilherme Amadio
2024-07-02 23:40     ` Namhyung Kim
2024-07-03 19:36       ` Steven Rostedt
2024-07-03 21:33         ` Namhyung Kim [this message]
2024-07-03 23:05           ` Steven Rostedt
2024-07-04  1:45             ` Namhyung Kim
2024-06-28 20:34   ` [PATCH v2 4/6] tools/verification: Use pkg-config in lib_setup of Makefile.config Guilherme Amadio
2024-06-28 20:34   ` [PATCH v2 5/6] tools/rtla: " Guilherme Amadio
2024-06-28 20:34   ` [PATCH v2 6/6] tools/latency: " Guilherme Amadio
2024-07-02 23:33   ` [PATCH v2 1/6] perf build: Conditionally add feature check flags for libtrace{event,fs} Namhyung Kim
2024-07-03 12:35     ` Guilherme Amadio
2024-07-03 21:29       ` Namhyung Kim
2024-07-11 22:08       ` Namhyung Kim
2024-07-08 12:32   ` Leo Yan
2024-07-16 10:19   ` Thorsten Leemhuis

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=ZoXDoajJqDiIcgwg@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=amadio@gentoo.org \
    --cc=irogers@google.com \
    --cc=leo.yan@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=rostedt@goodmis.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 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.