mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesper Juhl <juhl-lkml@dif.dk>
To: Robert Love <rml@novell.com>
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 19:46:50 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.62.0504261944020.2071@dragon.hyggekrogen.localhost> (raw)
In-Reply-To: <1114536937.6851.1.camel@betsy>

On Tue, 26 Apr 2005, Robert Love wrote:

> 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's not really that big of a deal. I was just currious if I'd gotten it 
right since I spend a good deal of time digging for possible reasons for 
the differences (and finding none). :-)

> 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.
> 
I'll update the patch(es) then and use __s32 in the structure and s32 
elsewhere.

> Acked-by: Robert Love <rml@novell.com>
> 
Thanks.

> 	Robert Love
> 

-- 
Jesper Juhl



  reply	other threads:[~2005-04-26 17:45 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
2005-04-26 17:46     ` Jesper Juhl [this message]
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=Pine.LNX.4.62.0504261944020.2071@dragon.hyggekrogen.localhost \
    --to=juhl-lkml@dif.dk \
    --cc=kpreempt-tech@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@novell.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 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®