From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <521DD7D9.6040108@siemens.com>
Date: Wed, 28 Aug 2013 12:58:33 +0200
From: Jan Kiszka <jan.kiszka@siemens.com>
MIME-Version: 1.0
References: <521DD3DD.6010300@siemens.com>
In-Reply-To: <521DD3DD.6010300@siemens.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Xenomai] IPIPE_KEVT_SETAFFINITY
List-Id: Discussions about the Xenomai project <xenomai.xenomai.org>
List-Unsubscribe: <http://www.xenomai.org/mailman/options/xenomai>,
	<mailto:xenomai-request@xenomai.org?subject=unsubscribe>
List-Archive: <http://www.xenomai.org/pipermail/xenomai>
List-Post: <mailto:xenomai@xenomai.org>
List-Help: <mailto:xenomai-request@xenomai.org?subject=help>
List-Subscribe: <http://www.xenomai.org/mailman/listinfo/xenomai>,
	<mailto:xenomai-request@xenomai.org?subject=subscribe>
To: Philippe Gerum <rpm@xenomai.org>
Cc: Xenomai <xenomai@xenomai.org>

On 2013-08-28 12:41, Jan Kiszka wrote:
> Hi Philippe,
> 
> please push to ipipe.git what introduces IPIPE_KEVT_SETAFFINITY. I'm
> riding on the tip of all trees and cannot build forge anymore.

Ah, oversaw it. It's in stable ipipe-3.8 only. Will pick it up for my
master queue.

> Or does
> this event rather require some feature detection in forge?

I suppose the policy for forge is still to require latest, full-featured
I-pipe patches, right?

Jan