From: "Bryan O'Sullivan" <bos@serpentine.com>
To: Andi Kleen <ak@suse.de>
Cc: vojtech@suse.cz, discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] New x86_64 time code for 2.5.70
Date: 11 Jun 2003 12:56:52 -0700 [thread overview]
Message-ID: <1055361411.17154.83.camel@serpentine.internal.keyresearch.com> (raw)
In-Reply-To: <20030611191815.GA30411@wotan.suse.de>
On Wed, 2003-06-11 at 12:18, Andi Kleen wrote:
> Does it only look this way or is your white space really broken?
I generated the patch with diff -b because my original changes fixed up
a lot of broken whitespace, which somewhat obscured the functional
changes. I'll send the plain diff -u instead next time.
> On UP the sync_core is not really needed, but more reliable. May be worth
> it to stick into an #ifdef though.
OK.
> > }
> >
> > + call++;
> > +
>
> What's that?
Oops - a piece of instrumentation that got left behind from trying to
fix an SMP deadlock.
<b
next prev parent reply other threads:[~2003-06-11 19:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 18:50 Bryan O'Sullivan
2003-06-11 19:18 ` Andi Kleen
2003-06-11 19:56 ` Bryan O'Sullivan [this message]
2003-06-11 20:10 ` Bryan O'Sullivan
2003-06-11 21:23 ` john stultz
2003-06-11 21:36 ` Bryan O'Sullivan
2003-06-11 21:41 ` john stultz
2003-06-12 0:33 ` john stultz
2003-06-12 6:40 ` Vojtech Pavlik
2003-06-12 17:47 ` Bryan O'Sullivan
2003-06-12 19:39 ` john stultz
2003-06-12 19:55 ` Vojtech Pavlik
2003-06-12 21:16 ` Bryan O'Sullivan
2003-06-13 1:43 ` john stultz
2003-06-12 19:48 ` Vojtech Pavlik
2003-06-11 20:41 ` Vojtech Pavlik
2003-06-11 20:44 ` john stultz
2003-06-11 21:32 ` Mika Penttilä
2003-06-11 21:28 ` Bryan O'Sullivan
2003-06-12 4:40 ` [discuss] " Andreas Jaeger
2003-06-12 6:42 ` Vojtech Pavlik
2003-06-12 6:47 ` Vojtech Pavlik
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=1055361411.17154.83.camel@serpentine.internal.keyresearch.com \
--to=bos@serpentine.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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
all inboxes | Powered by JetHome®