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 1/3] libperf: Move libperf under tools/lib/perf
Date: Fri, 6 Dec 2019 16:38:21 +0100 [thread overview]
Message-ID: <20191206153821.GE31721@krava> (raw)
In-Reply-To: <20191206153351.GA13965@kernel.org>
On Fri, Dec 06, 2019 at 12:33:51PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Dec 06, 2019 at 04:07:06PM +0100, Jiri Olsa escreveu:
> > On Fri, Dec 06, 2019 at 11:27:54AM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Fri, Dec 06, 2019 at 02:55:11PM +0100, Jiri Olsa escreveu:
> > > > Moving libperf from its current location under perf
> > > > to separate directory under tools/lib.
> > >
> > > Breaks the build/bisection:
> >
> > yes, I noted that in the cover email, the 2nd patch repairs paths,
> > but those changes would get lost in the move.. I can squash it
> > if you want, but I thought this is more transparent despite the
> > one-commit-long broken bisect ;-)
>
> It may well be, but bisection for me is of primary importance, so please
> avoid breaking it,
ok, will squash it and send new version
thanks,
jirka
next prev parent reply other threads:[~2019-12-06 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 13:55 [PATCH 0/3] perf/libperf move Jiri Olsa
2019-12-06 13:55 ` [PATCH 1/3] libperf: Move libperf under tools/lib/perf Jiri Olsa
2019-12-06 14:27 ` Arnaldo Carvalho de Melo
2019-12-06 15:07 ` Jiri Olsa
2019-12-06 15:33 ` Arnaldo Carvalho de Melo
2019-12-06 15:38 ` Jiri Olsa [this message]
2019-12-06 13:55 ` [PATCH 2/3] libperf: Additional fixes Jiri Olsa
2019-12-06 13:55 ` [PATCH 3/3] libperf: Add man pages Jiri Olsa
2019-12-06 14:21 ` [PATCH 0/3] perf/libperf move Arnaldo Carvalho de Melo
2019-12-06 14:34 ` 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=20191206153821.GE31721@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox