From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH] __deprecated not defined for Linux 2.4
Date: Mon, 09 Jul 2007 17:30:10 +0200 [thread overview]
Message-ID: <1183995010.6014.102.camel@domain.hid> (raw)
In-Reply-To: <469250F0.9080601@domain.hid>
On Mon, 2007-07-09 at 17:14 +0200, Jan Kiszka wrote:
> Wolfgang Grandegger wrote:
> > Jan Kiszka wrote:
> >> Philippe Gerum wrote:
> >>> On Mon, 2007-07-09 at 16:45 +0200, Wolfgang Grandegger wrote:
> >>>> Hello,
> >>>>
> >>>> the attached patch changes:
> >>>>
> >>>> 2007-07-09 Wolfgang Grandegger <wg@domain.hid>
> >>>>
> >>>> * include/asm-generic/wrappers.h: add __deprecated for Linux 2.4.
> >>>>
> >>> Merged, thanks.
> >>
> >> You are too fast for me - I was still test-building my approach!
> >
> > Too fast? My i-Pipe patched Linux 2.4 kernel did simply not built ;-).
>
> Yeah, and my 2.4 kernel was lying around in the corner, slightly dusty,
> definitely not touched for several months.
>
> Hell, the amount of regressions one (specifically I) can produce due to
> all this config variants is amazing.
We all have a very well defined job in this project, and particularly:
- I do produce the original silly bugs.
- You are in charge of adding regressions to your past fixes of my bugs
- Dmitry is in charge of finding why our common code breaks.
- Wolfgang is in charge of making all the involved fixes compile
properly.
- Gilles is in charge of making the result run on bugous and/or sluggish
hardware.
Ok, all in all, my situation is the best one. Good.
> What would be really nice is a
> playground for patches, some build system you could post a patch series
> and a set of .configs to and that will then "simply" try to generate
> various kernels and the xenomai userland for various archs
> automatically, reporting back any errors or warnings. Without going
> through SVN with the changes every time. Just a dream.
Niklaus already built most of this infrastructure for us, only the
automated patching part seems to be missing so far:
http://ngiger.dyndns.org/buildbot/
We would also have to alleviate the burden of his server by providing
some dedicated hardware to do that, though.
>
> Jan
>
--
Philippe.
next prev parent reply other threads:[~2007-07-09 15:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 14:45 [Xenomai-core] [PATCH] __deprecated not defined for Linux 2.4 Wolfgang Grandegger
2007-07-09 14:46 ` Philippe Gerum
2007-07-09 14:50 ` Jan Kiszka
2007-07-09 14:59 ` Philippe Gerum
2007-07-09 15:02 ` Jan Kiszka
2007-07-09 15:09 ` Philippe Gerum
2007-07-09 15:32 ` Wolfgang Grandegger
2007-07-09 15:32 ` Philippe Gerum
2007-07-09 15:11 ` Wolfgang Grandegger
2007-07-09 15:14 ` Jan Kiszka
2007-07-09 15:30 ` Philippe Gerum [this message]
2007-07-09 15:57 ` Jan Kiszka
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=1183995010.6014.102.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=xenomai@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.