All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [PATCH v2 0/5] NMI watchdog fixes / enhancements
Date: Tue, 23 Dec 2008 20:21:51 +0100	[thread overview]
Message-ID: <49513A4F.2060700@domain.hid> (raw)
In-Reply-To: <20081223190649.26094.61372.stgit@domain.hid>

Jan Kiszka wrote:
> Changes since last round:
>  - Fix build breakage of trunk against 2.6.27
>  - Make rthal_nmi_release more robust (additional patch)
>  - Fix issue of last patch on 32 bit (untested last-minute changes...)
> 
> All patches are also available at
> git://git.kiszka.org/xenomai.git nmi-wd-queue

I remind you that trunk is currently broken for the posix skin on arm, a
regression introduced by your FASTSYNCH patches. From my point of view,
fixing this regression is more important than fixing an option that
almost nobody uses with untested patches...

-- 
					    Gilles.


  parent reply	other threads:[~2008-12-23 19:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-23 19:06 [Xenomai-core] [PATCH v2 0/5] NMI watchdog fixes / enhancements Jan Kiszka
2008-12-23 19:06 ` [Xenomai-core] [PATCH v2 3/5] x86: Clear perfctr_msr on rthal_nmi_release Jan Kiszka
2008-12-23 19:06 ` [Xenomai-core] [PATCH v2 2/5] Update NMI watchdog for latest Intel CPUs Jan Kiszka
2008-12-23 19:06 ` [Xenomai-core] [PATCH v2 4/5] NMI watchdog support for x86-64 Jan Kiszka
2008-12-23 19:06 ` [Xenomai-core] [PATCH v2 1/5] x86_32: Fix NMI watchdog build for 2.6.27 Jan Kiszka
2008-12-23 19:06 ` [Xenomai-core] [PATCH v2 5/5] Rework x86 NMI watchdog pass-through Jan Kiszka
2008-12-23 19:21 ` Gilles Chanteperdrix [this message]
2008-12-24  0:57   ` [Xenomai-core] [PATCH v2 0/5] NMI watchdog fixes / enhancements Jan Kiszka
2008-12-24  7:25     ` Gilles Chanteperdrix
2008-12-29 14:32       ` Jan Kiszka
2008-12-29 16:36         ` Gilles Chanteperdrix

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=49513A4F.2060700@domain.hid \
    --to=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.