From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@domain.hid>, xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] crashing 2.6.22
Date: Tue, 09 Oct 2007 11:11:01 +0200 [thread overview]
Message-ID: <1191921061.22917.72.camel@domain.hid> (raw)
In-Reply-To: <2ff1a98a0710080145x2317ebc4ga4974a17abf22bdf@domain.hid>
On Mon, 2007-10-08 at 10:45 +0200, Gilles Chanteperdrix wrote:
> > Ooops. By reading all my mails, I would have avoided reinventing
> this
> > wheel on my own. Your patch is almost what I posted yesterday to fix
> the
> > vmalloc issue.
> >
> > Looks like we no longer need the last hunk of it on recent kernels,
> right?
>
> Yes, it fixes an issue which was fixed a long time ago.
>
Yeah, my mistake. I've postponed this patch and forgot to push it
forward again after the testing period in my cooker. Sorry about that.
> > Jan
> >
> > PS: We should really consider using bug trackers for Adeos and
> Xenomai!
> > I have a few (minor) patches hanging around as well, but things
> quickly
> > get lost when bigger problems pop up.
>
> We have bug trackers, the point is think about using them.
Indeed. We even have patch trackers we could activate. Either we use
them, or any patch sent for inclusion should be posted in a separate
mail to the -core list, with a [PATCH] header. I'm sometimes missing
them because they are part of a lengthy conversation, buried under lots
of mail I could fast-forward a bit aggressively.
>
--
Philippe.
next prev parent reply other threads:[~2007-10-09 9:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 14:09 [Xenomai-help] Non-APIC setup broken for 2.4-SVN? Jan Kiszka
2007-09-25 14:25 ` Leopold Palomo-Avellaneda
2007-09-25 21:37 ` Philippe Gerum
2007-09-26 9:31 ` Jan Kiszka
2007-09-30 10:22 ` Jan Kiszka
2007-09-30 10:52 ` Philippe Gerum
2007-09-30 11:00 ` Jan Kiszka
2007-09-30 11:42 ` [Xenomai-core] crashing 2.6.22 (was: [Xenomai-help] Non-APIC setup broken for 2.4-SVN?) Jan Kiszka
2007-09-30 12:42 ` Philippe Gerum
2007-09-30 15:31 ` [Xenomai-core] crashing 2.6.22 Jan Kiszka
2007-09-30 20:04 ` Philippe Gerum
2007-10-01 9:04 ` Gilles Chanteperdrix
2007-10-01 9:17 ` Jan Kiszka
2007-10-01 9:23 ` Gilles Chanteperdrix
2007-10-01 9:32 ` Jan Kiszka
2007-10-01 9:38 ` Gilles Chanteperdrix
2007-10-01 12:12 ` [Xenomai-core] ARM compiling error Patrick
2007-10-01 12:25 ` Gilles Chanteperdrix
[not found] ` <200710011255.l91CtkvR000470@domain.hid>
2007-10-01 13:10 ` Gilles Chanteperdrix
2007-10-01 13:43 ` Patrick
2007-10-01 14:29 ` Gilles Chanteperdrix
2007-10-01 12:42 ` [Xenomai-core] crashing 2.6.22 Labozzetta, Saverio
2007-10-01 13:32 ` Labozzetta, Saverio
2007-10-02 9:04 ` [Xenomai-help] rt_task crash kernel Patrick
2007-10-02 9:11 ` Gilles Chanteperdrix
[not found] ` <200710020940.l929ep0p021831@domain.hid>
2007-10-02 9:46 ` [Xenomai-core] " Gilles Chanteperdrix
2007-10-08 7:33 ` [Xenomai-core] crashing 2.6.22 Jan Kiszka
2007-10-08 8:45 ` Gilles Chanteperdrix
2007-10-09 9:11 ` Philippe Gerum [this message]
2007-09-30 19:45 ` [Xenomai-core] crashing 2.6.22 (was: [Xenomai-help] Non-APIC setup broken for 2.4-SVN?) Philippe Gerum
2007-09-30 19:52 ` [Xenomai-help] Non-APIC setup broken for 2.4-SVN? Philippe Gerum
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=1191921061.22917.72.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=gilles.chanteperdrix@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.