public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Alexis Berlemont <alexis.berlemont@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: perf and Kconfig
Date: Fri, 20 Dec 2013 19:05:13 -0800	[thread overview]
Message-ID: <52B50569.8060909@infradead.org> (raw)
In-Reply-To: <CAMesUR48C3zBo_UJByjC9GSqK6V=W_-WDQrsAoGye2yNADD3NQ@mail.gmail.com>

On 12/20/13 16:39, Alexis Berlemont wrote:
> Hi,
> 
> Here is a proposal of a small contribution which tries to fulfill the
> task "Use Kconfig to allow selecting features and build minimal
> version of perf,..." displayed on the todo page of the perf
> wiki (https://perf.wiki.kernel.org/index.php/Todo).
> 
> I tried to continue the work started by David Ahern
> (https://github.com/dsahern/linux.git branch:perf-config). This
> version relies on the features detection tests available in
> linux/tools/perf/config/feature-checks so as to enable some
> configuration options (at least by default).
> 
> This little task is not complete; more Kconfig options should be added
> for each perf tool (top, record, report, ...).
> 
> I just wanted to ask whether you consider this proposal as interesting
> enough for inclusion and if you are ok with the way it is implemented.
> 
> The code is available here: https://github.com/aberlemont/linux.git
> - branch: perf-config.

Hi,

The correct way to have any code reviewed is to post the code (not a link
to it) on the mailing list.

thanks,
-- 
~Randy

      parent reply	other threads:[~2013-12-21  3:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-21  0:39 perf and Kconfig Alexis Berlemont
2013-12-21  1:00 ` David Ahern
2013-12-23 11:54   ` Jiri Olsa
2013-12-28  0:16     ` Alexis Berlemont
2013-12-21  3:05 ` Randy Dunlap [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=52B50569.8060909@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=alexis.berlemont@gmail.com \
    --cc=linux-kernel@vger.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