From: David Miller <davem@davemloft.net>
To: sshah@solarflare.com
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [PATCH net v4 1/2] sfc: use 64-bit writes for PIO.
Date: Tue, 03 Jun 2014 15:58:07 -0700 (PDT) [thread overview]
Message-ID: <20140603.155807.2227032324368753328.davem@davemloft.net> (raw)
In-Reply-To: <538D9DB3.4080905@solarflare.com>
From: Shradha Shah <sshah@solarflare.com>
Date: Tue, 3 Jun 2014 11:04:35 +0100
> + writeq(src64[i], dest64+i);
What does writeq() do on a 32-bit machine?
Did you do any functional testing of this on such a machine?
I'm extremely disappointed in this patch submission, because you
didn't even _compile_ test this in the environment where you claim
the problem exists.
A 32-bit build with this patch applied results in:
CC drivers/net/ethernet/sfc/tx.o
drivers/net/ethernet/sfc/tx.c: In function ‘efx_memcpy_64’:
drivers/net/ethernet/sfc/tx.c:203:3: error: implicit declaration of function ‘writeq’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[1]: *** [drivers/net/ethernet/sfc/tx.o] Error 1
make: *** [drivers/net/ethernet/sfc/tx.o] Error 2
This is an extremely _LOW_ quality patch submission.
You put very little time and effort into the changes I asked you to
make. And clearly you did absolutely not functional testing of this
change, what if with the modification it didn't fix the bug any
longer?
It is imperitive that you take your time and go implement these
changes properly. Yes, you can clearly see now that a proper
interface for writeq() is not provided that actually uses 64-bit
operations on 32-bit systems. And yes, _you_ will need to resolve
this somehow.
And most importantly, you will need to both compile and functionally
test the change before you even think about posting it again here.
Thanks.
next prev parent reply other threads:[~2014-06-03 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 10:02 [PATCH net v4 0/2] sfc: Restrict PIO for 64bit arch in order to avoid data corruption Shradha Shah
2014-06-03 10:04 ` [PATCH net v4 1/2] sfc: use 64-bit writes for PIO Shradha Shah
2014-06-03 16:45 ` Sergei Shtylyov
2014-06-03 17:55 ` Joe Perches
2014-06-03 22:58 ` David Miller [this message]
2014-06-05 17:08 ` Robert Stonehouse
2014-06-03 10:05 ` [PATCH net v4 2/2] sfc: Restrict PIO to 64-bit architectures Shradha Shah
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=20140603.155807.2227032324368753328.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=sshah@solarflare.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;
as well as URLs for NNTP newsgroup(s).