All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Michael Petlan <mpetlan@redhat.com>
Subject: Re: [PATCH] perf tools: Unify a bit the build directory output
Date: Thu, 19 Mar 2020 20:26:53 +0100	[thread overview]
Message-ID: <20200319192653.GA1200613@krava> (raw)
In-Reply-To: <20200319185750.GE14841@kernel.org>

On Thu, Mar 19, 2020 at 03:57:50PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Mar 19, 2020 at 03:25:14PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Wed, Mar 18, 2020 at 09:45:22PM +0100, Jiri Olsa escreveu:
> > > Removing the extra 'SUBDIR' line from clean and doc build
> > > output. Because it's annoying.. ;-)
> > > 
> > > Before:
> > >   $ make clean
> > >   ...
> > >   SUBDIR   Documentation
> > >   CLEAN    Documentation
> > > 
> > > After:
> > >   $ make clean
> > >   ...
> > >   CLEAN    Documentation
> > 
> > Thanks, applied to perf/core.
> 
> Hey, since you're annoyed, how about sending a patch to ditch this one:
> 
> make[3]: Nothing to be done for '/tmp/build/perf/plugins/libtraceevent-dynamic-list'.
> 
> ? ;-)

I'll add it to my 'when annoyed todo list' .. which is getting
more and more attention in this lock down time ;-)

jirka


  reply	other threads:[~2020-03-19 19:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 20:45 [PATCH] perf tools: Unify a bit the build directory output Jiri Olsa
2020-03-19 18:25 ` Arnaldo Carvalho de Melo
2020-03-19 18:57   ` Arnaldo Carvalho de Melo
2020-03-19 19:26     ` Jiri Olsa [this message]
2020-04-04  8:41 ` [tip: perf/urgent] " tip-bot2 for Jiri Olsa

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=20200319192653.GA1200613@krava \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mpetlan@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 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.