All of lore.kernel.org
 help / color / mirror / Atom feed
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 00/02] staging:lustre:lnet:selftest: fix sparse warnings
Date: Wed, 29 Oct 2014 08:29:43 +0400	[thread overview]
Message-ID: <cover.1414517099.git.antonysaraev@gmail.com> (raw)

Patch fix simple sparse warnings: make functions static and remove
unused code. I'm doing only little testing: module was loaded properly,
output of lst without real server is the same as before.

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


             reply	other threads:[~2014-10-29  4:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29  4:29 Anton Saraev [this message]
2014-10-29  4:29 ` [PATCH 01/02] staging:lustre:lnet:selftest: fix sparse warnings Anton Saraev
2014-10-29  8:37   ` [PATCH v2 " Greg KH
2014-10-29  4:29 ` [PATCH 02/02] staging:lustre:lnet:selftest: remove unused function Anton Saraev
2014-10-29  8:37   ` [PATCH v2 " Greg KH

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.1414517099.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 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.