From: SF Markus Elfring <elfring@users.sourceforge.net>
To: ltp@lists.linux.it
Subject: [LTP] InfiniBand-ocrdma: Delete unnecessary variable initialisations in 11 functions
Date: Sat, 16 Jan 2016 09:30:22 +0100 [thread overview]
Message-ID: <5699FF9E.3030708@users.sourceforge.net> (raw)
In-Reply-To: <20160116061843.GE32346@leon.nu>
> Please provide the numbers BEFORE and AFTER your change which can
> support that your so called "fine-tuning" worked.
For which combinations of hardware and software versions would you
like to see corresponding results from detailed system checks
and special benchmarks?
> We are waiting to see it together with Tested-By tag to emphasize
> that your code was tested on real HW and passed minimal sanity checks.
Are any other contributors interested to collaborate for such a task?
> NAK on this patch.
Thanks for your feedback.
Does it mean that you reject (only) the proposed source code adjustments
around the variable "status" in the shown function selection at the moment?
Would you like to clarify the other update steps from this patch series
a bit more?
Regards,
Markus
parent reply other threads:[~2016-01-16 8:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20160116061843.GE32346@leon.nu>]
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=5699FF9E.3030708@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=ltp@lists.linux.it \
/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