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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110518181305.GB8190@elte.hu>
Date:	Wed, 18 May 2011 20:13:05 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 00/15] [GIT PULL] ftrace/recordmcount: cleanups and
 updates for recordmcount processing


* Steven Rostedt <rostedt@...dmis.org> wrote:

> On Wed, 2011-05-18 at 12:08 -0400, Steven Rostedt wrote:
> > Ingo,
> > 
> > Please pull the latest tip/perf/core-2 tree, which can be found at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> > tip/perf/core-2
> > 
> 
> Note, this is not based off of my tip/perf/core branch, but is based off
> of tip separately.

I pulled your tip/perf/core (b9df92d2a94e) on May 1, almost 3 weeks ago, into 
tip:perf/core.

> I'm not sure why you don't want to pull my tip/perf/core directly yet.

Because i already have? :-)

> [...] I'd like to get that infrastructure in and tested before the 40 merge 
> window so that we can focus on the perf function tracing in the 41 window, 
> and not try to figure out where bugs are between the two.
> 
> That pull request is here:
> 
>   http://marc.info/?l=linux-kernel&m=130469692420787

Well, that is an RFC patchset, named:

 [RFC][PATCH 00/13] ftrace: Allow multiple users to pick and choose functions

In that mail you specifically said:

 " I'm posting this patch series as an RFC, but I do not expect it to change 
   much. I still have to put it through more tests even though I ran several on 
   each set already. "

... with no pull vector in it. If you want me to pull something you need to put 
it into a branch i can see and you need to send a pull request :-)

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ