All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Mauerer <wolfgang.mauerer@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>,
	"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] [GIT PULL] core-5 for x86
Date: Tue, 18 Sep 2012 17:27:36 +0200	[thread overview]
Message-ID: <505892E8.6080605@siemens.com> (raw)
In-Reply-To: <50588458.1010802@xenomai.org>

On 18/09/12 16:25, Gilles Chanteperdrix wrote:
> On 09/18/2012 04:11 PM, Wolfgang Mauerer wrote:
>> Dear all,
>>
>> here's a rebase of the x86-specific bits of core-4 to core-5. I've
>> included all x86 specific changes that are not yet in core-5, and
>> also added the patches I sent earlier for core-4. I did not include a
>> separate patch for the mechanical changes required to apply the
>> x86 base patch on top of core-5, but can surely do so if desired.
> 
> I am not quite finished with x86 on 3.4. So, I would like to start 3.5
> from the finishing point on 3.4. There are already commits in my branch
> which you did not take:
> 
> http://git.xenomai.org/?p=ipipe-gch.git;a=shortlog;h=refs/heads/for-core-3.4
that's true; my last pull was too old. I'll add the corresponding
commits to the tree (FYI, the purpose of this tree is mainly to do some
experiments with the latest ipipe release and the latest kernel, and
I wanted to make sure that work is not duplicated in case someone else
is pursuing similar goals)
> 
> This is assuming that I am the (flaky subsitute for a) maintainer of the
> x86 architecture. Of course, if someone wants to take over the
> maintenance of the x86 architecture, I am gladly returning to the ARMs.
> 
> 4-x86 applied to core-5
>>       x86/ipipe: Make io_apic_level_ack_pending available for ipipe
> 
> What is this commit? Neither the text nor the diff are very explicit.
yes, this commit is fairly big considering its small effect. I've updated
the description as follows:

Make sure that io_apic_level_ack_pending() is compiled in when ipipe is
configured. Also move the implementation downwards so that it is
not referenced before it is defined.

Best regards, Wolfgang


  reply	other threads:[~2012-09-18 15:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18 14:11 [Xenomai] [GIT PULL] core-5 for x86 Wolfgang Mauerer
2012-09-18 14:25 ` Gilles Chanteperdrix
2012-09-18 15:27   ` Wolfgang Mauerer [this message]
2012-09-18 19:36     ` Gilles Chanteperdrix
2012-09-19 12:15       ` Wolfgang Mauerer
2012-09-19 12:36         ` Gilles Chanteperdrix
2012-09-20 16:11         ` Gilles Chanteperdrix
2012-09-25 14:45           ` Wolfgang Mauerer
2012-09-25 14:57             ` Gilles Chanteperdrix
2012-09-25 14:58               ` Wolfgang Mauerer
2012-09-26 14:41               ` Wolfgang Mauerer
2012-09-26 13:16                 ` [Xenomai] [PATCH 1/2] Refactor ipipe_select_timers Wolfgang Mauerer
2012-09-26 21:28                   ` Gilles Chanteperdrix
2012-09-27  8:28                     ` Wolfgang Mauerer
2012-09-27 12:04                       ` Gilles Chanteperdrix
2012-09-27 12:47                         ` Wolfgang Mauerer
2012-09-27 12:54                           ` Gilles Chanteperdrix
2012-09-27 12:56                             ` Wolfgang Mauerer
2012-09-27 18:33                           ` Gilles Chanteperdrix
2012-09-28  8:32                             ` Wolfgang Mauerer
2012-09-30 20:50                               ` Gilles Chanteperdrix
2012-09-26 13:16                 ` [Xenomai] [PATCH 2/2] Register high-res timer irq for non-ipipe timers if necessary Wolfgang Mauerer
2012-09-27 18:39                   ` 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=505892E8.6080605@siemens.com \
    --to=wolfgang.mauerer@siemens.com \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=jan.kiszka@siemens.com \
    --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.