public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-next@vger.kernel.org
Subject: Re: Linux 4.0-rc1 out..
Date: Tue, 24 Feb 2015 14:40:34 -0500	[thread overview]
Message-ID: <20150224194034.GA3042@home.goodmis.org> (raw)
In-Reply-To: <20150223161541.22df98cc@canb.auug.org.au>

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
> 

      parent reply	other threads:[~2015-02-24 19:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+55aFzS==STcTbwabdvw=7_xX08kkUd=g2Q4XbWJzKbpjyN1A@mail.gmail.com>
2015-02-23  5:15 ` Linux 4.0-rc1 out Stephen Rothwell
2015-02-23  8:22   ` Sedat Dilek
2015-02-23 23:14   ` Olof Johansson
2015-02-24 19:40   ` Steven Rostedt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150224194034.GA3042@home.goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox