From: Clark Williams <williams@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: John Kacur <jkacur@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
rt-users <linux-rt-users@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH-RT] preempt.h: Fix implicit declaration of 'preempt_check_resched_rt'
Date: Thu, 8 Mar 2012 14:22:57 -0600 [thread overview]
Message-ID: <20120308142257.145e0968@redhat.com> (raw)
In-Reply-To: <1331237840.25686.470.camel@gandalf.stny.rr.com>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On Thu, 08 Mar 2012 15:17:20 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Thu, 2012-03-08 at 21:13 +0100, John Kacur wrote:
> > When building a non-preempt kernel where CONFIG_PREEMPT_COUNT is not
> > defined the following build break occurs.
> >
> > /home/jkacur/linux-rt/block/blk-softirq.c: In function ‘trigger_softirq’:
> > /home/jkacur/linux-rt/block/blk-softirq.c:54: error: implicit declaration of function ‘preempt_check_resched_rt’
> > make[2]: *** [block/blk-softirq.o] Error 1
> > make[1]: *** [block/blk-softirq.o] Error 2
> > make: *** [sub-make] Error 2
> >
> > This patch fixes the build error by adding a define to the
> > !CONFIG_PREEMPT_COUNT section.
> >
> > Signed-off-by: Clark Williams <williams@redhat.com>
>
> Why Clark's SOB? Did he write it and send it to you?
I suppose to be technically correct it should have been a Tested-by:
John found it while I was working on it and I tested it for him.
Clark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-03-08 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 20:13 [PATCH-RT] preempt.h: Fix implicit declaration of 'preempt_check_resched_rt' John Kacur
2012-03-08 20:17 ` Steven Rostedt
2012-03-08 20:22 ` Clark Williams [this message]
2012-03-08 20:34 ` Steven Rostedt
2012-03-08 21:04 ` John Kacur
2012-03-13 19:24 ` Steven Rostedt
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=20120308142257.145e0968@redhat.com \
--to=williams@redhat.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--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