From: David Woodhouse <dwmw2@infradead.org>
To: root@chaos.analogic.com
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 17:07:31 +0100 [thread overview]
Message-ID: <1066406850.6744.1462.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0310171143450.3689@chaos>
On Fri, 2003-10-17 at 11:49 -0400, Richard B. Johnson wrote:
> Well it isn't RBJcode. It's Intel code. Look who wrote it
> before you give me any credit, especially your kind of "credit".
You deserve the same 'credit' for quoting code from a known purveyor of
crap code as you'd deserve for writing it yourself. Although to their
credit Intel do seem to be capable of writing slightly better code these
days than they used to.
> Also, Intel machines have 32-bit longs which are identical to
> 32-bit ints and this was an Intel driver........
Even some Intel machines have 64-bit longs nowadays. Certainly there's
no excuse for that particular error. It's just a gratuitous
non-portability.
> Have fun growing up.
You have to let me have fun -- it's boring just correcting you every
time you mislead a newbie.
I wouldn't bother if you weren't just picking on people who don't know
better, but if you're going to cruelly post utterly broken code in
response to a genuine question, someone needs to say something.
--
dwmw2
prev parent reply other threads:[~2003-10-17 16:07 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
2003-10-17 16:07 ` David Woodhouse [this message]
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=1066406850.6744.1462.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=Suresh.Subramanian@lntinfotech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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®