public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RT: update rcurefs for RT
Date: Fri, 30 Sep 2005 02:55:50 +0200	[thread overview]
Message-ID: <1128041750.15115.367.camel@tglx.tec.linutronix.de> (raw)
In-Reply-To: <1128007259.11511.4.camel@c-67-188-6-232.hsd1.ca.comcast.net>

On Thu, 2005-09-29 at 08:20 -0700, Daniel Walker wrote:
> +static inline void init_rcurefs(void)
> +{
> +	int i;
> +	for (i=0; i < RCUREF_HASH_SIZE; i++) 
> +		__rcuref_hash[i] = SPIN_LOCK_UNLOCKED(__rcuref_hash[i]);

Maybe a simple 

	spin_lock_init(&__rcuref_hash[i]);

would work all over tha place ?

tglx



  reply	other threads:[~2005-09-30  0:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 18:32 [PATCH] RT: update rcurefs for RT Daniel Walker
2005-09-28  9:32 ` Ingo Molnar
2005-09-29 11:42 ` Ingo Molnar
2005-09-29 15:20   ` Daniel Walker
2005-09-30  0:55     ` Thomas Gleixner [this message]
2005-09-30  8:34       ` Ingo Molnar
2005-09-30 14:17         ` Daniel Walker

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=1128041750.15115.367.camel@tglx.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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