From: Paolo Ornati <ornati-dbx96nzIXN7OeuqD6ShaSA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Michal Piotrowski
<michal.k.k.piotrowski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Linux-MRDXTZLjjMs8G+1z+Pypc6QD96bmaF075NbjCUgZEJk@public.gmane.org
Subject: Re: WARNING: at arch/x86_64/kernel/smp.c:379 smp_call_function_single()
Date: Sun, 19 Aug 2007 14:51:36 +0200 [thread overview]
Message-ID: <20070819145136.5d9f0adb@localhost> (raw)
In-Reply-To: <46C82191.90300-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Sun, 19 Aug 2007 13:55:13 +0300
Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
> Sorry about the delay -- here is the fairly simple patch. A Tested-by:
> would be appreciated.
it works :)
Tested-by: Paolo Ornati <ornati-dbx96nzIXN7OeuqD6ShaSA@public.gmane.org>
--
Paolo Ornati
Linux 2.6.23-rc3-g2a677896-dirty on x86_64
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-08-19 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070810134140.2806b587@localhost>
2007-08-10 12:04 ` WARNING: at arch/x86_64/kernel/smp.c:379 smp_call_function_single() Michal Piotrowski
[not found] ` <6bffcb0e0708100504n7fbafb5bt6a35165277dc767a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-13 11:42 ` Paolo Ornati
2007-08-13 12:35 ` Avi Kivity
2007-08-19 10:55 ` Avi Kivity
[not found] ` <46C82191.90300-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-19 12:51 ` Paolo Ornati [this message]
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=20070819145136.5d9f0adb@localhost \
--to=ornati-dbx96nzixn7oeuqd6shasa@public.gmane.org \
--cc=Linux-MRDXTZLjjMs8G+1z+Pypc6QD96bmaF075NbjCUgZEJk@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michal.k.k.piotrowski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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