linux-kernel - Re: [PATCH 00/10] [GIT PULL] tracing: various fixes

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]

Date:	Mon, 5 Dec 2011 10:47:18 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 00/10] [GIT PULL] tracing: various fixes


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

> On Sat, 2011-12-03 at 10:20 +0100, Ingo Molnar wrote:
> 
> > Hm, not all were regression fixes and the branch was named 
> > */core so i took it into perf/core.
> 
> Yeah it happened just at the end of the merge window. I didn't really
> know what branch to name it.
> 
> > 
> > Could you perhaps cherry-pick the most crutial regression 
> > fixes into an urgent branch? We could still push that 
> > upstream.
> 
> Looking at each patch, I would say 6 of the ten need to go in. 
> Most are marked as stable since they break the last tree. I 
> could just send them all to stable if it seems strange to have 
> this many patches in two pull requests.

We can cherry-pick those 6 patches into perf/urgent - just make 
sure you merge the cherry-picked branch into your devel branch 
before adding new changes to the same files, there will be tons 
of conflicts otherwise.

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/