linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Drokin <green@linuxhacker.ru>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org,
	Andreas Dilger <andreas.dilger@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lustre Development List <lustre-devel@lists.lustre.org>,
	Oleg Drokin <green@linuxhacker.ru>
Subject: [PATCH 0/8] Lustre: Multiple assignments removal.
Date: Thu,  9 Jun 2016 22:35:10 -0400	[thread overview]
Message-ID: <1465526118-521053-1-git-send-email-green@linuxhacker.ru> (raw)

These patches remove multiple assignments in Lustre, that makes
checkpatch (somewhat understandably) unhappy.

Nathaniel Clark (8):
  staging/lustre/osc: Fix Multiple Assignment Warnings
  staging/lustre/fid: Fix Multiple Assignments
  staging/lustre/ldlm: Fix Multiple Assignments
  staging/lustre/llite: Fix Multiple Assignments
  staging/lustre/lov: Fix Multiple Assignments
  staging/lustre/obdclass: Fix Multiple Assignments
  staging/lustre/ptlrpc: Fix Multiple Assignments
  staging/lustre/lmv: Fix Multiple Assignments

 drivers/staging/lustre/lustre/fid/fid_request.c     |  6 ++++--
 drivers/staging/lustre/lustre/ldlm/ldlm_lib.c       |  3 ++-
 drivers/staging/lustre/lustre/ldlm/ldlm_lockd.c     |  8 +++++---
 drivers/staging/lustre/lustre/llite/llite_lib.c     |  3 ++-
 drivers/staging/lustre/lustre/llite/namei.c         |  3 ++-
 drivers/staging/lustre/lustre/llite/vvp_io.c        |  3 ++-
 drivers/staging/lustre/lustre/lmv/lmv_obd.c         |  3 +--
 drivers/staging/lustre/lustre/lov/lov_obd.c         |  9 ++++-----
 drivers/staging/lustre/lustre/obdclass/llog.c       |  6 ++++--
 drivers/staging/lustre/lustre/osc/osc_cache.c       |  6 ++++--
 drivers/staging/lustre/lustre/osc/osc_io.c          | 12 ++++++++----
 drivers/staging/lustre/lustre/osc/osc_lock.c        |  3 ++-
 drivers/staging/lustre/lustre/osc/osc_request.c     |  6 ++++--
 drivers/staging/lustre/lustre/ptlrpc/client.c       |  6 ++++--
 drivers/staging/lustre/lustre/ptlrpc/import.c       |  3 ++-
 drivers/staging/lustre/lustre/ptlrpc/lproc_ptlrpc.c |  3 ++-
 drivers/staging/lustre/lustre/ptlrpc/pinger.c       |  3 ++-
 drivers/staging/lustre/lustre/ptlrpc/sec_null.c     |  3 ++-
 18 files changed, 56 insertions(+), 33 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-06-10  2:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-10  2:35 Oleg Drokin [this message]
2016-06-10  2:35 ` [PATCH 1/8] staging/lustre/osc: Fix Multiple Assignment Warnings Oleg Drokin
2016-06-10  2:35 ` [PATCH 2/8] staging/lustre/fid: Fix Multiple Assignments Oleg Drokin
2016-06-10  2:35 ` [PATCH 3/8] staging/lustre/ldlm: " Oleg Drokin
2016-06-10  2:35 ` [PATCH 4/8] staging/lustre/llite: " Oleg Drokin
2016-06-10  2:35 ` [PATCH 5/8] staging/lustre/lov: " Oleg Drokin
2016-06-10  2:35 ` [PATCH 6/8] staging/lustre/obdclass: " Oleg Drokin
2016-06-10  2:35 ` [PATCH 7/8] staging/lustre/ptlrpc: " Oleg Drokin
2016-06-10  2:35 ` [PATCH 8/8] staging/lustre/lmv: " Oleg Drokin
2016-06-15 20:15 ` [PATCH 0/8] Lustre: Multiple assignments removal Luis de Bethencourt

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=1465526118-521053-1-git-send-email-green@linuxhacker.ru \
    --to=green@linuxhacker.ru \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lustre-devel@lists.lustre.org \
    /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).