Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752552AbbBXTkh (ORCPT ); Tue, 24 Feb 2015 14:40:37 -0500 Received: from cdptpa-outbound-snat.email.rr.com ([107.14.166.231]:44559 "EHLO cdptpa-oedge-vip.email.rr.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752166AbbBXTkg (ORCPT ); Tue, 24 Feb 2015 14:40:36 -0500 Date: Tue, 24 Feb 2015 14:40:34 -0500 From: Steven Rostedt To: Stephen Rothwell Cc: Linus Torvalds , Linux Kernel Mailing List , linux-next@vger.kernel.org Subject: Re: Linux 4.0-rc1 out.. Message-ID: <20150224194034.GA3042@home.goodmis.org> References: <20150223161541.22df98cc@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150223161541.22df98cc@canb.auug.org.au> User-Agent: Mutt/1.5.23 (2014-03-12) X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1115 Lines: 36 On Mon, Feb 23, 2015 at 04:15:41PM +1100, Stephen Rothwell wrote: > > There are also 265 commits in next-20150209 that didn't make it into > v4.0-rc1. > > Top ten first word of commit summary: > > 25 rcu > 24 arm > 20 selftests > 19 mm > 11 arm-soc > 6 documentation > 5 tracing Yep, that was my tracefs code. It's all ready to go mainline, but then I did some stress testing on perf, and found that perf hard coded the mount id into itself, and ignored traceevents if they were not in the debugfs system (even if the path was the same!). I sent patches to fix this but because those patches didn't make it into the release, I decide to not push this knowing it will cause issues with perf. Thus, tracefs needs to wait till perf is updated before I push it out. -- Steve > 5 staging > 5 libceph > 5 ceph > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/