All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Skvortsov <andrej.skvortzov@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, andreas.dilger@intel.com,
	sachin.kamat@linaro.org, bergwolf@gmail.com,
	linux-kernel@vger.kernel.org
Subject: [PATCHv2 0/3] staging: lustre: obdclass: fixing coding style issues
Date: Thu, 19 Jun 2014 11:24:09 +0400	[thread overview]
Message-ID: <1403162653-17845-1-git-send-email-Andrej.Skvortzov@gmail.com> (raw)
In-Reply-To: <20140618223533.GA5096@kroah.com>

Changes since PATCHv1:

I refreshed patch against the staging-next branch of the staging.git tree
and added some other coding style fixes as separate patches.


Andrey Skvortsov (3):
  staging: lustre: obdclass: linux-sysctl.c: fix pointer coding style
    issue
  staging: lustre: obdclass: linux-sysctl.c: fix checkpatch warnings
    about included headers
  staging: lustre: obdclass: linux-sysctl.c: fix unnecessary spaces
    coding style issue

 .../lustre/lustre/obdclass/linux/linux-sysctl.c    |   20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

-- 
1.7.10.4


  reply	other threads:[~2014-06-19  7:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 15:27 [PATCH] staging: lustre: obdclass: linux-sysctl.c: fix pointer coding style issue Andrey Skvortsov
2014-06-18 22:35 ` Greg KH
2014-06-19  7:24   ` Andrey Skvortsov [this message]
2014-06-19  7:24     ` [PATCHv2 1/3] " Andrey Skvortsov
2014-06-19  7:24       ` Andrey Skvortsov
2014-06-19  7:24         ` [PATCHv2 2/3] staging: lustre: obdclass: linux-sysctl.c: fix checkpatch warnings about included headers Andrey Skvortsov
2014-06-19  7:24           ` [PATCHv2 3/3] staging: lustre: obdclass: linux-sysctl.c: fix unnecessary spaces coding style issue Andrey Skvortsov

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=1403162653-17845-1-git-send-email-Andrej.Skvortzov@gmail.com \
    --to=andrej.skvortzov@gmail.com \
    --cc=andreas.dilger@intel.com \
    --cc=bergwolf@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sachin.kamat@linaro.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 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.