All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Emde <Carsten.Emde@osadl.org>
To: Clark Williams <williams@redhat.com>
Cc: John Kacur <jkacur@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-rt-users@vger.kernel.org
Subject: Re: [PATCH 3/4] rt-tests: Clean-up - protect rt-utils.h
Date: Tue, 22 Dec 2009 00:43:40 +0100	[thread overview]
Message-ID: <4B30082C.80107@osadl.org> (raw)
In-Reply-To: <20091221171913.5ae81e6d@torg>

[-- Attachment #1: Type: text/plain, Size: 781 bytes --]

Clark,

>>> Clean-up: Protect rt-utils.h with #ifndef RT_UTILS_H
>>> [..]
>>> +#ifndef RT_UTILS.H
>> Macro names should only consist of alphanumeric characters and
>> underscores, i.e. 'a-z', 'A-Z', '0-9', and '_', and the first character
>> should not be a digit.
> Yeah, I caught that and also pushed it out of application name space
> with two leading underscores. 
Great.

I did some first tests on 0.58, and all works very well now. Thanks a
lot, you and John, for all the work!

As a very minor issue, the below patch still didn't make it into your
tree.

	Carsten.

-=--------------------------------------------------------------------=-
Explain in the sendme error message how to make the backfire module,
if not available.

Signed-off-by: Carsten Emde <C.Emde@osadl.org>

[-- Attachment #2: explain-howto-make-backfire-module.patch --]
[-- Type: text/x-patch, Size: 657 bytes --]

diff --git a/src/backfire/sendme.c b/src/backfire/sendme.c
index fdc1056..1f02c72 100644
--- a/src/backfire/sendme.c
+++ b/src/backfire/sendme.c
@@ -209,7 +209,12 @@ int main(int argc, char *argv[])
 	path = open("/dev/backfire", O_RDWR);
 	if (path < 0) {
 		fprintf(stderr, "ERROR: Could not access backfire device, "
-				"try 'modprobe backfire'\n");
+				"try 'modprobe backfire'.\n"
+				"If the module backfire can't be loaded, "
+				"it may need to be built first.\n"
+				"Execute 'cd src/backfire; make' in the "
+				"rt-tests directory (requires rt-tests\n"
+				"sources and kernel-devel package).\n");
 		return 1;
 	}
 	fl.l_type = F_WRLCK;

  reply	other threads:[~2009-12-21 23:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 21:45 [PATCH 0/4] *** Add a get_cpu() library *** John Kacur
2009-12-21 21:45 ` [PATCH 1/4] rt-tests: Makefile - Changes to unify and simplify the Makefile John Kacur
2009-12-21 21:45   ` [PATCH 2/4] rt-tests: Add a get_cpu() function to the library John Kacur
2009-12-21 21:45     ` [PATCH 3/4] rt-tests: Clean-up - protect rt-utils.h John Kacur
2009-12-21 21:45       ` [PATCH 4/4] Completely remove VERSION_STRING until we have a better solution John Kacur
2009-12-21 23:09       ` [PATCH 3/4] rt-tests: Clean-up - protect rt-utils.h Carsten Emde
2009-12-21 23:19         ` Clark Williams
2009-12-21 23:43           ` Carsten Emde [this message]
2009-12-21 23:41         ` John Kacur
2009-12-21 22:54 ` [PATCH 0/4] *** Add a get_cpu() library *** Clark Williams

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=4B30082C.80107@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.