From: Carsten Emde <Carsten.Emde@osadl.org>
To: John Kacur <jkacur@redhat.com>
Cc: Clark Williams <williams@redhat.com>,
linux-rt-users@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: More RT Test Programs
Date: Mon, 21 Dec 2009 00:49:26 +0100 [thread overview]
Message-ID: <4B2EB806.301@osadl.org> (raw)
In-Reply-To: <520f0cf10912201451q55c823cbia07c23f4a3bbe98c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
John,
> [..] I'll be posting some more tomorrow.
Okay, great.
I have found an issue with all source files of the new tests. At some
stage between the original files and Clark's tree, the line delimiters
changed from NL to CR/NL. Would be great, if you could move this back to NL.
A second issue is related to the removal of the getcpu() definition.
There is a leftover in svsematest.c which should also be removed for
consistency. However, this and the other tests no longer compile in EL5
without this definition - should we better revert this and provide a
working recognition through "grep sched_getcpu
/usr/include/bits/sched.h"? Or is EL5 irrelevant in this context? I
still have an EL5 test machine where all RT kernels are tested.
Another issue is in the file backfire.c After you removed the line
>> - sed s/__VERSION_STRING__/$(VERSION_STRING)/ [..]
from the Makefile, the driver is producing the rather ugly syslog message:
backfire driver v__VERSION_STRING__
instead of
backfire driver v0.57
or similar.
We better completely remove the version display.
Signed-off-by: Carsten Emde <C.Emde@osadl.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: fix-backfire-version-display.patch --]
[-- Type: text/x-patch; name="fix-backfire-version-display.patch", Size: 396 bytes --]
--- backfire.c-orig 2009-12-20 22:40:48.000000000 +0100
+++ backfire.c 2009-12-20 22:41:40.000000000 +0100
@@ -132,7 +132,7 @@
if (ret)
printk(KERN_ERR "backfire: can't register dynamic misc device\n");
else
- printk(KERN_INFO "backfire driver v__VERSION_STRING__ misc device %d\n",
+ printk(KERN_INFO "backfire driver misc device %d\n",
backfire_dev.minor);
return ret;
}
next prev parent reply other threads:[~2009-12-20 23:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <388070393.1730301260825543554.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
[not found] ` <4B26B838.1080303@osadl.org>
2009-12-14 23:55 ` More RT Test Programs John Kacur
2009-12-20 20:42 ` Carsten Emde
2009-12-20 22:51 ` John Kacur
2009-12-20 23:49 ` Carsten Emde [this message]
2009-12-21 0:08 ` John Kacur
[not found] ` <520f0cf10912201605y4019b940p346c73b927a52b39@mail.gmail.com>
2009-12-21 2:10 ` Carsten Emde
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=4B2EB806.301@osadl.org \
--to=carsten.emde@osadl.org \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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).