public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "David S. Miller" <davem@redhat.com>
Cc: rusty@rustcorp.com.au, torvalds@transmeta.com,
	linux-kernel@vger.kernel.org, rgooch@ras.ucalgary.ca
Subject: Re: bit ops on unsigned long?
Date: Mon, 18 Mar 2002 01:03:30 -0500	[thread overview]
Message-ID: <3C958332.4050508@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0203151656320.1379-100000@home.transmeta.com>	<E16m4YD-0004af-00@wagner.rustcorp.com.au> <20020317.200828.64296429.davem@redhat.com>

David S. Miller wrote:

>   From: Rusty Russell <rusty@rustcorp.com.au>
>   Date: Sat, 16 Mar 2002 14:08:08 +1100
>
>   +#ifdef CONFIG_PREEMPT
>    	/* Set the preempt count _outside_ the spinlocks! */
>    	idle->thread_info->preempt_count = (idle->lock_depth >= 0);
>   +#endif
>
>This part of your patch has to go.  Every port must
>provide the preempt_count member of thread_info regardless
>of the CONFIG_PREEMPT setting.
>

Even if the port doesn't support CONFIG_PREEMPT at all?

    Jeff







  reply	other threads:[~2002-03-18  6:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-16  0:52 bit ops on unsigned long? Rusty Russell
2002-03-16  0:58 ` Linus Torvalds
2002-03-16  3:08   ` Rusty Russell
2002-03-18  4:08     ` David S. Miller
2002-03-18  6:03       ` Jeff Garzik [this message]
2002-03-18  6:43         ` David S. Miller
2002-03-18  9:13         ` Rusty Russell
2002-03-25  2:45     ` Richard Gooch
2002-03-25  4:27       ` Rusty Russell
2002-03-25  6:21         ` Richard Gooch
2002-03-25  7:07           ` Rusty Russell
2002-03-25  7:12             ` Richard Gooch
2002-03-16  1:00 ` Anton Blanchard

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=3C958332.4050508@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@transmeta.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