The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Daniel Walker <dwalker@mvista.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -rt 2/2] arm update
Date: Thu, 18 May 2006 10:06:54 +0200	[thread overview]
Message-ID: <20060518080654.GE30387@elte.hu> (raw)
In-Reply-To: <200605141557.k4EFv5Sd004979@dwalker1.mvista.com>


* Daniel Walker <dwalker@mvista.com> wrote:

>  - Fixed arm mcount/arm_return_addr so they aren't under OABI_COMPAT ifdefs .
>  - adds a new NR_syscalls macro, converts the old one into __NR_syscalls for
>    calculating the table padding .
>  - removes old semaphore __MUTEX_INITIALIZER()
>  - depends blocker on X86 
>  - updates clockfw_lock to a raw_spinlock_t

thanks, applied.

	Ingo

  reply	other threads:[~2006-05-18  8:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-14 15:57 [PATCH -rt 2/2] arm update Daniel Walker
2006-05-18  8:06 ` Ingo Molnar [this message]
2006-05-18 13:53 ` Nicolas Pitre
2006-05-18 14:27   ` Daniel Walker
2006-05-18 15:26     ` Nicolas Pitre

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=20060518080654.GE30387@elte.hu \
    --to=mingo@elte.hu \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox