From: Jeremy Fitzhardinge <jeremy@xensource.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: paravirt_ops queue rebased
Date: Mon, 07 May 2007 11:14:45 -0700 [thread overview]
Message-ID: <463F6C95.10103@xensource.com> (raw)
In-Reply-To: <1178558797.3729.21.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> The original one you sent had duplicate smp_call_function...
> definitions. The interdiff between the one you've attached now and the
> one I sent is pretty tiny:
>
Huh. Must have been a mixup somewhere, because this was one was more or
less identical to the last one. Maybe I'd sent out an earlier borken
one you picked up? Anyway, doesn't matter.
> + u32 mask = cpus_addr(cpumask)[0];
>
Ah, didn't know about that.
J
next prev parent reply other threads:[~2007-05-07 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 17:21 paravirt_ops queue rebased Jeremy Fitzhardinge
2007-05-06 18:12 ` James Bottomley
2007-05-06 23:27 ` Jeremy Fitzhardinge
[not found] ` <1178558797.3729.21.camel@mulgrave.il.steeleye.com>
2007-05-07 18:14 ` Jeremy Fitzhardinge [this message]
2007-05-06 21:49 ` Andi Kleen
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=463F6C95.10103@xensource.com \
--to=jeremy@xensource.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=virtualization@lists.osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).