lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161019131106.GB25522@kernel.org>
Date:   Wed, 19 Oct 2016 10:11:06 -0300
From:   Arnaldo Carvalho de Melo <acme@...nel.org>
To:     Jiri Olsa <jolsa@...hat.com>
Cc:     "Jin, Yao" <yao.jin@...ux.intel.com>, jolsa@...nel.org,
        Linux-kernel@...r.kernel.org, ak@...ux.intel.com,
        kan.liang@...el.com, Ingo Molnar <mingo@...nel.org>
Subject: Re: [PATCH 0/6] Show branch flags/cycles in perf report
 --branch-history callgraph view

Em Wed, Oct 19, 2016 at 10:55:34AM +0200, Jiri Olsa escreveu:
> On Wed, Oct 19, 2016 at 04:46:02PM +0800, Jin, Yao wrote:
> > It's based on the current branch "remotes/origin/perf/core" of tip
> > (https://kernel.googlesource.com/pub/scm/linux/kernel/git/tip/tip.git).
> > 
> > Should the patch be based on the branch "remotes/origin/perf/core" of the
> > repo (https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git)?
> 
> yep, that's what we do normaly.. because Arnaldo has already
> some other new patches pilled up

Yeah, please use acme/perf/core, I'll split it into more manageable
chunks and get them feed to Ingo, when he starts processing perf/core
pull requests.

The first one to get into probably is the perf/vendor_events branch.

- Arnaldo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ