mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: John Kacur <jkacur@redhat.com>
Cc: Paul McKenney <paulmck@linux.vnet.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH] rcutree: Fix v3.4-rc2-rt2 build break
Date: Thu, 12 Apr 2012 21:46:16 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1204122142180.2542@ionos> (raw)
In-Reply-To: <1334155379-18088-1-git-send-email-jkacur@redhat.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1238 bytes --]

On Wed, 11 Apr 2012, John Kacur wrote:

> Fix build break of the following types.
> 
> linux-rt/kernel/rcutree_plugin.h: In function ‘print_cpu_stall_fast_no_hz’:
> linux-rt/kernel/rcutree_plugin.h:2195: error: ‘rcu_idle_gp_timer’ undeclared (first use in this function)
> linux-rt/kernel/rcutree_plugin.h:2195: error: (Each undeclared identifier is reported only once
> linux-rt/kernel/rcutree_plugin.h:2195: error: for each function it appears in.)
> 
> The build break only occurs with the PREEMPT_RT_FULL patch applied, however
> the patch is meant to go upstream and be applied to v3.4-rc2 as well because
> it makes the code more legible there, and will reduce the number of places
> where #ifdef PREEMPT_RT_FULL is required should that go upstream someday.

-ENOPARSE

I really have no idea what the patch is solving and which particular
combination of config items is causing the above.

If you think that the patch should go upstream then please send a
separate one with a changelog which explains the simplifcation.

I agree that this ifdef maze can do with simplification, but providing
a changelog which tells nothing at all does not make it easier to grok
the problem and understand what's simplified.

Thanks,

	tglx

  reply	other threads:[~2012-04-12 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 14:42 John Kacur
2012-04-12 19:46 ` Thomas Gleixner [this message]
2012-04-12 23:11   ` Paul E. McKenney
2012-04-12 23:13   ` John Kacur

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=alpine.LFD.2.02.1204122142180.2542@ionos \
    --to=tglx@linutronix.de \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.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®