From: Steven Rostedt <rostedt@goodmis.org>
To: Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/2] tracing: Fixes to event_triggers patches found by Fengguang's test bot
Date: Thu, 2 Jan 2014 12:11:00 -0500 [thread overview]
Message-ID: <20140102121100.5f09ffb9@gandalf.local.home> (raw)
In-Reply-To: <1387768382.14728.9.camel@empanada>
On Sun, 22 Dec 2013 21:13:02 -0600
Tom Zanussi <tom.zanussi@linux.intel.com> wrote:
> Hi Steve,
>
> On Sat, 2013-12-21 at 22:07 -0500, Steven Rostedt wrote:
> > Tom,
> >
> > This is the changes I made to fix the reports that Fengguang's kbuild test bot
> > found. I folded in your change that fixes the bug with -ENODEV used in kernel.h.
> >
>
> These look fine to me, and I didn't see any problems after running
> through my normal event trigger testing with them applied.
>
> So you can add my Acked-by and/or Tested-by..
>
> Thanks for writing these improved versions!
Bah, I forgot to add these to the change logs before pushing to my
for-next branch. I hate to rebase, but I also would like these tags
too.
Hmm, I may just rebase anyway. We still have a couple of weeks before
the merge window opens.
-- Steve
prev parent reply other threads:[~2014-01-02 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 3:07 Steven Rostedt
2013-12-22 3:08 ` [PATCH 1/2] tracing: Add generic tracing_lseek() function Steven Rostedt
2013-12-22 3:08 ` [PATCH 2/2] tracing: Fix rcu handling of event_trigger_data filter field Steven Rostedt
2014-01-09 1:30 ` Paul E. McKenney
2013-12-23 3:13 ` [PATCH 0/2] tracing: Fixes to event_triggers patches found by Fengguang's test bot Tom Zanussi
2014-01-02 17:11 ` 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=20140102121100.5f09ffb9@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tom.zanussi@linux.intel.com \
/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
all inboxes | Powered by JetHome®