All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: "Santos, Jose Renato G" <joserenato.santos@hp.com>,
	xen-devel@lists.xensource.com
Subject: Re: [PATCH] Add find_domain_rcu_lock() and domain_rcu_unlock functions
Date: Wed, 21 Feb 2007 16:33:35 +0000	[thread overview]
Message-ID: <C20224DF.9DC8%keir@xensource.com> (raw)
In-Reply-To: <08CA2245AFCF444DB3AC415E47CC40AF757F08@G3W0072.americas.hpqcorp.net>


The RCU patches so far are now checked in, so you can carry on to actually
make use of find_domain_rcu_lock() now. By the way I changed some of the
function prototypes to take extra (dummy arguments) to make code more self
documenting. So you'll want to obtain latest xen-unstable once the RCU
patches have passed the regression tests and been pushed to the public tree,
and base further patches off that.

 -- Keir

On 9/2/07 19:29, "Santos, Jose Renato G" <joserenato.santos@hp.com> wrote:

> Sorry,
> Forgot to attach the file in previous message
> 
> Renato 
> 
>> -----Original Message-----
>> From: Santos, Jose Renato G
>> Sent: Friday, February 09, 2007 11:28 AM
>> To: Keir Fraser; xen-devel@lists.xensource.com
>> Subject: [PATCH] Add find_domain_rcu_lock() and
>> domain_rcu_unlock functions
>> 
>> 
>> Keir,
>> 
>> This patch adds find_domain_rcu_lock() and
>> domain_rcu_unlock() functions that we have discussed before.
>> 
>> Thanks 
>> 
>> Renato
>> 
>> 

  reply	other threads:[~2007-02-21 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 19:29 [PATCH] Add find_domain_rcu_lock() and domain_rcu_unlock functions Santos, Jose Renato G
2007-02-21 16:33 ` Keir Fraser [this message]
2007-02-21 17:53   ` Santos, Jose Renato G
  -- strict thread matches above, loose matches on Subject: below --
2007-02-09 19:27 Santos, Jose Renato G

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=C20224DF.9DC8%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=joserenato.santos@hp.com \
    --cc=xen-devel@lists.xensource.com \
    /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.