From: Steven Rostedt <rostedt@goodmis.org>
To: Joel Fernandes <joelaf@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-team@android.com, Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v8 1/2] tracing: Prepare to add preempt and irq trace events
Date: Tue, 10 Oct 2017 18:44:41 -0400 [thread overview]
Message-ID: <20171010184441.200e66f0@gandalf.local.home> (raw)
In-Reply-To: <CAJWu+oq+KT2r5v-02d_-CLeVSm82s6Gwp_tq_FSaYSAsEHHxJQ@mail.gmail.com>
On Tue, 10 Oct 2017 15:32:27 -0700
Joel Fernandes <joelaf@google.com> wrote:
> On Tue, Oct 10, 2017 at 3:19 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Thu, 5 Oct 2017 17:54:31 -0700
> > Joel Fernandes <joelaf@google.com> wrote:
> >
> >> In preparation of adding irqsoff and preemptsoff enable and disable trace
> >> events, move required functions and code to make it easier to add these events
> >> in a later patch. This patch is just code movement and no functional change.
> >
> > New warning:
> >
> > kernel/trace/trace_irqsoff.c:783:69: warning: 'tracing_irq_cpu' defined but not used [-Wunused-variable]
> >
> > Looks pretty obvious what the fix is. Care to send a v9?
>
> Yes, I'll fix it and send a v9. Sorry about that.
>
Just send the patch for this one. Don't need to send a series.
Heck, call it v8.1 ;-)
-- Steve
next prev parent reply other threads:[~2017-10-10 22:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 0:54 [PATCH v8 0/2] tracing: Add trace events for preemption and irq disable/enable Joel Fernandes
2017-10-06 0:54 ` [PATCH v8 1/2] tracing: Prepare to add preempt and irq trace events Joel Fernandes
2017-10-10 22:19 ` Steven Rostedt
2017-10-10 22:32 ` Joel Fernandes
2017-10-10 22:44 ` Steven Rostedt [this message]
2017-10-10 22:54 ` Joel Fernandes
2017-10-06 0:54 ` [PATCH v8 2/2] tracing: Add support for preempt and irq enable/disable events Joel Fernandes
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=20171010184441.200e66f0@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=joelaf@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®