From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Rui Sousa <rui.p.m.sousa@gmail.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATH] Fix compilation when CONFIG_TRACE_IRQFLAGS_SUPPORT is not set
Date: Thu, 04 Sep 2008 10:14:03 -0700 [thread overview]
Message-ID: <48C0175B.3070500@ct.jp.nec.com> (raw)
In-Reply-To: <20080904143918.GA28095@elte.hu>
Ingo Molnar wrote:
> * Rui Sousa <rui.p.m.sousa@gmail.com> wrote:
>
>> Hi,
>>
>> This patch fixes compilation if CONFIG_TRACE_IRQFLAGS_SUPPORT is ever
>> disabled (which is currently not allowed by Kconfig). Alternatively we
>> could just remove the option altogether and the associated code paths.
>> Since the compilation error has been in the tree for at least two
>> years and no one noticed it, I guess we don't really have the need for
>> CONFIG_TRACE_IRQFLAGS_SUPPORT=n. Boot tested on x86 UP.
>
> applied to tip/core/locking - thanks Rui.
>
> since you fixed it i prefer the fix over the removal. We could still
> remove the !TRACE_IRQFLAGS_SUPPORT now (in a separate commit) and
> simpify this header a bit that way. Thus if someone needs the
> !TRACE_IRQFLAGS_SUPPORT mode of build for future work, it can be
> restored via a simple revert.
Hi, it seems that this patch breaks uml build.
kernel/printk.c: In function 'vprintk':
kernel/printk.c:674: error: implicit declaration of function 'raw_local_irq_save'
kernel/printk.c:772: error: implicit declaration of function 'raw_local_irq_restore'
thanks,
Hiroshi Shimamoto
next prev parent reply other threads:[~2008-09-04 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 15:53 [PATH] Fix compilation when CONFIG_TRACE_IRQFLAGS_SUPPORT is not set Rui Sousa
2008-09-04 14:39 ` Ingo Molnar
2008-09-04 17:14 ` Hiroshi Shimamoto [this message]
2008-09-04 17:47 ` Rui Sousa
2008-09-04 18:29 ` Hiroshi Shimamoto
2008-09-05 10:57 ` Ingo Molnar
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=48C0175B.3070500@ct.jp.nec.com \
--to=h-shimamoto@ct.jp.nec.com \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rui.p.m.sousa@gmail.com \
--cc=tglx@linutronix.de \
/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