From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: davem@dm.cobaltmicro.com (David S. Miller)
Cc: fisher@sgi.com, linux@hollywood.engr.sgi.com,
fisher@hollywood.engr.sgi.com
Subject: Re: Pentium F00F bug Linux workaround; BSDI Response
Date: Mon, 17 Nov 1997 23:56:37 +0000 (GMT) [thread overview]
Message-ID: <m0xXb1y-0005FrC@lightning.swansea.linux.org.uk> (raw)
In-Reply-To: <199711172323.PAA27334@dm.cobaltmicro.com> from "David S. Miller" at Nov 17, 97 03:23:46 pm
> BSDI putting out their patch ahead of that point in time was, if
> anything, totally against how Intel wanted things happen.
Dave talk this off list. And if you are going to say things like
"XYZ violated their NDA" expect them to both hear about it and reply. Fair's
fair.
WARNING: multiple messages have this Message-ID (diff)
From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: "David S. Miller" <davem@dm.cobaltmicro.com>
Cc: fisher@sgi.com, linux@hollywood.engr.sgi.com,
fisher@hollywood.engr.sgi.com
Subject: Re: Pentium F00F bug Linux workaround; BSDI Response
Date: Mon, 17 Nov 1997 23:56:37 +0000 (GMT) [thread overview]
Message-ID: <m0xXb1y-0005FrC@lightning.swansea.linux.org.uk> (raw)
Message-ID: <19971117235637.XkCdmvdgByzSvfsHSRVNWUcOtfOw4z2gtmyv5PehLs4@z> (raw)
In-Reply-To: <199711172323.PAA27334@dm.cobaltmicro.com> from "David S. Miller" at Nov 17, 97 03:23:46 pm
> BSDI putting out their patch ahead of that point in time was, if
> anything, totally against how Intel wanted things happen.
Dave talk this off list. And if you are going to say things like
"XYZ violated their NDA" expect them to both hear about it and reply. Fair's
fair.
next prev parent reply other threads:[~1997-11-17 23:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-17 21:28 Pentium F00F bug Linux workaround; BSDI Response William Fisher
1997-11-17 21:28 ` William Fisher
1997-11-17 23:23 ` David S. Miller
1997-11-17 23:56 ` Alan Cox [this message]
1997-11-17 23:56 ` Alan Cox
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=m0xXb1y-0005FrC@lightning.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davem@dm.cobaltmicro.com \
--cc=fisher@hollywood.engr.sgi.com \
--cc=fisher@sgi.com \
--cc=linux@hollywood.engr.sgi.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.