mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Suresh Subramanian <Suresh.Subramanian@lntinfotech.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: killing a kernel thread.
Date: Fri, 17 Oct 2003 11:49:16 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0310171143450.3689@chaos> (raw)
In-Reply-To: <1066405067.6744.1444.camel@hades.cambridge.redhat.com>

On Fri, 17 Oct 2003, David Woodhouse wrote:

> Ooh ooh RBJcode. I'm going to be fair and only pick one of the errors,
> leaving many more for others to play the game too...
>
>
> On Fri, 2003-10-17 at 09:51 -0400, Richard B. Johnson wrote:
>
> >   __u32 volatile status;
>
> >   while (!test_bit(0,&priv->status)) {
>
> test_bit() and friends work on 'unsigned long' not uint32_t.
>
> --
> dwmw2
>

Well it isn't RBJcode. It's Intel code. Look who wrote it
before you give me any credit, especially your kind of "credit".

Also, Intel machines have 32-bit longs which are identical to
32-bit ints and this was an Intel driver........

Have fun growing up.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2003-10-17 15:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17 12:51 Suresh Subramanian
2003-10-17 13:51 ` Richard B. Johnson
2003-10-17 15:37   ` David Woodhouse
2003-10-17 15:49     ` Richard B. Johnson [this message]
2003-10-17 16:07       ` David Woodhouse

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.53.0310171143450.3689@chaos \
    --to=root@chaos.analogic.com \
    --cc=Suresh.Subramanian@lntinfotech.com \
    --cc=dwmw2@infradead.org \
    --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 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®