From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: adeos-main <adeos-main@gna.org>, Philippe Gerum <rpm@xenomai.org>
Subject: Re: [Adeos-main] [pull request] Avoid double bug reports
Date: Fri, 11 Dec 2009 14:46:29 +0100 [thread overview]
Message-ID: <4B224D35.8030500@domain.hid> (raw)
In-Reply-To: <4B2249E3.7030705@domain.hid>
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> The following changes since commit 88fd7426f3565647b4f5ef93d8e612e059dae873:
>> Philippe Gerum (1):
>> Make generic atomic ops Adeos-aware
>>
>> are available in the git repository at:
>>
>> git://git.kiszka.org/ipipe-2.6.git queues/2.6.31-noarch
>>
>> Jan Kiszka (2):
>> noarch: Don't check for internal errors during oops
>> noarch: Set oops_in_progress on failing context check
>>
>> kernel/ipipe/core.c | 6 +++---
>> 1 files changed, 3 insertions(+), 3 deletions(-)
>>
>> -------
>>
>> noarch: Don't check for internal errors during oops
>>
>> We are busted already, verifying the context here only generates
>> confusing output or causes even more corruptions.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>
>
> Are we sure this fixes all issues? Maybe we should wait for Josh tests
> before releasing another I-pipe patch?
I doesn't fix Josh's primary issue, it targets at some of the succeeding
errors he got (it doesn't make sense to complain about incorrect
contexts twice or more, specifically if the BUG_ONs provide less
information than the primary check).
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2009-12-11 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 11:51 [Adeos-main] [pull request] Avoid double bug reports Jan Kiszka
2009-12-11 13:32 ` Gilles Chanteperdrix
2009-12-11 13:46 ` Jan Kiszka [this message]
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=4B224D35.8030500@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=adeos-main@gna.org \
--cc=gilles.chanteperdrix@xenomai.org \
--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.