From: Karim Yaghmour <karim@domain.hid>
To: Arnaldo Carvalho de Melo <acme@domain.hid>
Cc: linux-kernel <linux-kernel@domain.hid>,
Adeos <adeos-main@gna.org>, Philippe Gerum <rpm@xenomai.org>
Subject: [Adeos-main] Re: [PATCH] Adeos nanokernel for 2.5.38 1/2: no-arch code
Date: Sun, 22 Sep 2002 23:09:39 -0400 [thread overview]
Message-ID: <3D8E85F3.D57C292F@opersys.com> (raw)
In-Reply-To: 20020923030312.GM20520@domain.hid
Arnaldo Carvalho de Melo wrote:
> Why this ifdef hell and not something like:
>
> lockbuf_lock();
> bla
> logbuf_unlock();
>
> and have this defined in a header, say printk.h or whatever, with the
> ifdefs?
You're right, this is somewhat insane ;)
We'll fix it, thanks.
Karim
===================================================
Karim Yaghmour
karim@domain.hid
Embedded and Real-Time Linux Expert
===================================================
WARNING: multiple messages have this Message-ID (diff)
From: Karim Yaghmour <karim@opersys.com>
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Adeos <adeos-main@mail.freesoftware.fsf.org>,
Philippe Gerum <rpm@xenomai.org>
Subject: Re: [PATCH] Adeos nanokernel for 2.5.38 1/2: no-arch code
Date: Sun, 22 Sep 2002 23:09:39 -0400 [thread overview]
Message-ID: <3D8E85F3.D57C292F@opersys.com> (raw)
In-Reply-To: 20020923030312.GM20520@conectiva.com.br
Arnaldo Carvalho de Melo wrote:
> Why this ifdef hell and not something like:
>
> lockbuf_lock();
> bla
> logbuf_unlock();
>
> and have this defined in a header, say printk.h or whatever, with the
> ifdefs?
You're right, this is somewhat insane ;)
We'll fix it, thanks.
Karim
===================================================
Karim Yaghmour
karim@opersys.com
Embedded and Real-Time Linux Expert
===================================================
next prev parent reply other threads:[~2002-09-23 3:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 2:58 [Adeos-main] [PATCH] Adeos nanokernel for 2.5.38 1/2: no-arch code Karim Yaghmour
2002-09-22 4:59 ` [Adeos-main] " Pavel Machek
2002-09-24 21:05 ` Karim Yaghmour
2002-09-24 21:05 ` Karim Yaghmour
2002-09-24 21:33 ` [Adeos-main] " Jacob Gorm Hansen
2002-09-24 23:15 ` Karim Yaghmour
2002-09-24 21:33 ` Jacob Gorm Hansen
2002-09-24 23:15 ` Karim Yaghmour
2002-09-24 22:06 ` Pavel Machek
2002-09-24 23:22 ` Karim Yaghmour
2002-09-25 8:17 ` Pavel Machek
2002-09-24 22:06 ` [Adeos-main] " Pavel Machek
2002-09-24 23:22 ` Karim Yaghmour
2002-09-25 8:17 ` Pavel Machek
2002-09-23 3:03 ` Arnaldo Carvalho de Melo
2002-09-23 3:09 ` Karim Yaghmour [this message]
2002-09-23 3:09 ` Karim Yaghmour
-- strict thread matches above, loose matches on Subject: below --
2002-09-23 2:58 Karim Yaghmour
2002-09-22 4:59 ` Pavel Machek
2002-09-23 3:03 ` Arnaldo Carvalho de Melo
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=3D8E85F3.D57C292F@opersys.com \
--to=karim@domain.hid \
--cc=acme@domain.hid \
--cc=adeos-main@gna.org \
--cc=linux-kernel@domain.hid \
--cc=rpm@xenomai.org \
/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.