From: Anton Saraev <antonysaraev@gmail.com>
To: gregkh@linuxfoundation.org
Cc: antonysaraev@gmail.com, oleg.drokin@intel.com,
andreas.dilger@intel.com, heenasirwani@gmail.com,
bergwolf@gmail.com, amir.shehata@intel.com, gdonald@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 00/02] staging:lustre:lnet:selftest: fix sparse warnings
Date: Wed, 29 Oct 2014 23:41:48 +0400 [thread overview]
Message-ID: <cover.1414609881.git.antonysaraev@gmail.com> (raw)
As I can understand warning in previous series is about unused function
(I don't see other differences in output of make with C=1, W=1 and W=2).
I remove "static" for lnet_selftest_structure_assertion from
first patch. Maybe I should merge patches in one but I think that
addition of static declaration and deletion of function should be in two
different patches. So the second patch depends on the first...
Anton Saraev (2):
staging:lustre:lnet:selftest: fix sparse warnings
staging:lustre:lnet:selftest: remove unused function
drivers/staging/lustre/lnet/selftest/conctl.c | 34 ++++++++--------
drivers/staging/lustre/lnet/selftest/conrpc.c | 20 +++++-----
drivers/staging/lustre/lnet/selftest/framework.c | 50 ++++++++++++------------
drivers/staging/lustre/lnet/selftest/module.c | 15 +------
drivers/staging/lustre/lnet/selftest/rpc.c | 34 ++++++++--------
drivers/staging/lustre/lnet/selftest/timer.c | 8 ++--
6 files changed, 75 insertions(+), 86 deletions(-)
--
1.9.1
next reply other threads:[~2014-10-29 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 19:41 Anton Saraev [this message]
2014-10-29 19:41 ` [PATCH v2 01/02] staging:lustre:lnet:selftest: fix sparse warnings Anton Saraev
2014-10-29 19:41 ` [PATCH v2 02/02] staging:lustre:lnet:selftest: remove unused function Anton Saraev
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=cover.1414609881.git.antonysaraev@gmail.com \
--to=antonysaraev@gmail.com \
--cc=amir.shehata@intel.com \
--cc=andreas.dilger@intel.com \
--cc=bergwolf@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gdonald@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heenasirwani@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.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