public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Michal Marek <michal.lkml@markovi.net>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH] scripts: dummy-tools, add pahole
Date: Tue, 19 Apr 2022 08:23:23 +0200	[thread overview]
Message-ID: <2a54f2da-cdc0-078a-5dce-d79a736e9ebc@kernel.org> (raw)
In-Reply-To: <CAK7LNATgfosGQ6LRmu8DUxwnWL=Dyu1cOUUq1GBRtP6+BppNbw@mail.gmail.com>

On 14. 04. 22, 17:18, Masahiro Yamada wrote:
>>> Well, the question is how do I that for every kernel developer in SUSE?
>>
>> IOW it'd be quite easier if the scripts/dummy-tools/pahole part of the
>> patch was in the tree. (I don't insist on the Makefile change.)
> 
> 
> I do not mind  scripts/dummy-tools/pahole

Perfect!

> although you need to do
> make CROSS_COMPILE=scripts/dummy-tools
> PAHOLE=scripts/dummy-tools/pahole  menuconfig

That's easy -- the developers use a script that I can modify. (Oppositng 
to writing files to their homes etc.)

Will send a v2.

thanks,
-- 
js
suse labs

      reply	other threads:[~2022-04-19  6:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14  9:14 [PATCH] scripts: dummy-tools, add pahole Jiri Slaby
2022-04-14  9:33 ` Masahiro Yamada
2022-04-14  9:42   ` Jiri Slaby
2022-04-14  9:44     ` Jiri Slaby
2022-04-14 15:18       ` Masahiro Yamada
2022-04-19  6:23         ` Jiri Slaby [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=2a54f2da-cdc0-078a-5dce-d79a736e9ebc@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=ndesaulniers@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox