From: Rusty Russell <rusty@rustcorp.com.au>
To: Jeff Garzik <jgarzik@mandrakesoft.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 20:13:10 +1100 [thread overview]
Message-ID: <E16mtCt-00013Y-00@wagner.rustcorp.com.au> (raw)
In-Reply-To: Your message of "Mon, 18 Mar 2002 01:03:30 CDT." <3C958332.4050508@mandrakesoft.com>
In message <3C958332.4050508@mandrakesoft.com> you write:
> 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.
Sorry, slipped in so I could compile on PPC. Discard that part of the
patch please.
Thanks,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-03-18 9:11 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
2002-03-18 6:43 ` David S. Miller
2002-03-18 9:13 ` Rusty Russell [this message]
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=E16mtCt-00013Y-00@wagner.rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
--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 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.