From: John Dykstra <john.dykstra1@gmail.com>
To: Don Fry <pcnet32@verizon.net>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, jeff@garzik.org
Subject: Re: [PATCH net-next-2.6] pcnet32: Remove pointless memory barriers
Date: Wed, 29 Apr 2009 14:07:57 -0500 [thread overview]
Message-ID: <1241032077.7487.16.camel@Maple> (raw)
In-Reply-To: <1241025057.17018.7.camel@localhost.localdomain>
On Wed, 2009-04-29 at 10:10 -0700, Don Fry wrote:
> How would this be tested on all architectures to find out?
Testing could never prove that the barriers _aren't_ needed, because
you'd never be sure that you'd hit the right conditions.
-- John
next prev parent reply other threads:[~2009-04-29 19:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 19:07 [PATCH net-next-2.6] pcnet32: Remove pointless memory barriers John Dykstra
2009-04-29 5:16 ` David Miller
2009-04-29 13:48 ` John Dykstra
2009-04-29 17:10 ` Don Fry
2009-04-29 19:07 ` John Dykstra [this message]
2009-04-29 22:29 ` Francois Romieu
2009-04-30 0:09 ` Don Fry
2009-04-30 0:16 ` John Dykstra
2009-04-30 0:21 ` David Miller
2009-04-30 0:19 ` David Miller
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=1241032077.7487.16.camel@Maple \
--to=john.dykstra1@gmail.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=pcnet32@verizon.net \
/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;
as well as URLs for NNTP newsgroup(s).