linux-kernel - Re: linux-next: build failure after merge of the ftrace tree

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: <20130302151700.89f98f5c132a913510b5a621@canb.auug.org.au>
Date:	Sat, 2 Mar 2013 15:17:00 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the ftrace tree

Hi Steve,

On Fri, 01 Mar 2013 22:55:29 -0500 Steven Rostedt <rostedt@...dmis.org> wrote:
>
> Oh crap, sorry. Quite the contrary. I should have waited for -rc1 as
> this is intended for v3.10.
> 
> I made some major changes and wanted testing on it as soon as possible.
> I've done tons of testing on my own but I wanted a broader audience. Do
> you want me to pull my tree and reset it to what is only for 3.9?

Yes, please.  The reasoning is that until -rc1 is out we don't want to
complicate life for people whose code has not yet been merged by
reporting problems in code that will not be merged until the next merge
window.

That is why my daily reports during the merge window start with:

"Please do not add any work destined for v3.10 to your -next included
branches until after Linus has release v3.9-rc1."

But I am beginning to realise that not many actually read those reports (I
had the date wrong on two of them this week and it was only noticed after
the second one :-().

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped