From: Henning Schild <henning.schild@siemens.com>
To: linux-rt-users@vger.kernel.org, Yang Shi <yang.shi@windriver.com>
Subject: regression in rt patches
Date: Mon, 7 Mar 2016 18:28:25 +0100	[thread overview]
Message-ID: <20160307182825.3647f443@md1em3qc> (raw)
Hey,
this patch out of the current 4.4.3-rt9 series
"trace: Use rcuidle version for preemptoff_hist trace point"
introduces a regression where the kernel wont compile for a
configuration without trace histograms
Ammend to following to the patch to fix it:
--- a/include/trace/events/hist.h
+++ b/include/trace/events/hist.h
@@ -9,6 +9,7 @@
 
 #if !defined(CONFIG_PREEMPT_OFF_HIST) && !defined(CONFIG_INTERRUPT_OFF_HIST)
 #define trace_preemptirqsoff_hist(a, b)
+#define trace_preemptirqsoff_hist_rcuidle(a, b)
 #else
 TRACE_EVENT(preemptirqsoff_hist,
Henning
next             reply	other threads:[~2016-03-07 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 17:28 Henning Schild [this message]
2016-03-07 23:55 ` regression in rt patches Yang Shi
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=20160307182825.3647f443@md1em3qc \
    --to=henning.schild@siemens.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=yang.shi@windriver.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;
as well as URLs for NNTP newsgroup(s).