From: Robert Love <rml@novell.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
kpreempt-tech@lists.sourceforge.net
Subject: Re: preempt-count oddities - still looking for comments :)
Date: Tue, 26 Apr 2005 13:35:37 -0400 [thread overview]
Message-ID: <1114536937.6851.1.camel@betsy> (raw)
In-Reply-To: <Pine.LNX.4.62.0504261929230.2071@dragon.hyggekrogen.localhost>
On Tue, 2005-04-26 at 19:31 +0200, Jesper Juhl wrote:
> Replying to myself here since the initial mail got no response. Here's
> hoping that it showing up on the list again draws some comments :-)
I didn't think it was that big of a deal. ;-)
It seems the right approach. Personally, I would of made the type an
s32, since fixed-sizes seems to be sensible in the thread_info
structure, but an int is the same thing. Cool with me.
Acked-by: Robert Love <rml@novell.com>
Robert Love
next prev parent reply other threads:[~2005-04-26 17:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 21:30 preempt-count oddities Jesper Juhl
2005-04-26 17:31 ` preempt-count oddities - still looking for comments :) Jesper Juhl
2005-04-26 17:35 ` Robert Love [this message]
2005-04-26 17:46 ` Jesper Juhl
2005-04-26 17:46 ` Robert Love
2005-04-26 17:57 ` Jesper Juhl
2005-04-26 20:05 ` Jesper Juhl
2005-04-26 20:28 ` Robert Love
2005-04-26 20:55 ` Jesper Juhl
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=1114536937.6851.1.camel@betsy \
--to=rml@novell.com \
--cc=juhl-lkml@dif.dk \
--cc=kpreempt-tech@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 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.