public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Berger <git.rber@gmail.com>
To: devel@driverdev.osuosl.org, konrad.wilk@oracle.com
Cc: gregkh@linuxfoundation.org, sjenning@linux.vnet.ibm.com,
	xiaoguangrong@linux.vnet.ibm.com, minchan@kernel.org,
	linux-kernel@vger.kernel.org, joe@perches.com,
	git.rber@gmail.com,
	Robert Berger <rber.git@ReliableEmbeddedSystems.com>
Subject: [PATCH 0/4] staging/zache KBUILD_MODNAME, checkpatch fixes
Date: Sat, 16 Feb 2013 10:35:50 +0200	[thread overview]
Message-ID: <1361003754-22512-1-git-send-email-rber.git@ReliableEmbeddedSystems.com> (raw)
In-Reply-To: <git.rber@gmail.com>

1) As per Joe's suggestion:

  "Perhaps it'd be better to use KBUILD_MODNAME all the time
  instead of adding the prefix. Also, to me mixing "ramster: "
  and "zcache: " for the prefixes is odd. Just using zcache
  all the time would be simpler, so remove namestr too."

2) Some checkpatch fixes

Robert Berger (4):
  fix: ERROR: spaces prohibited around that ':' (ctx:VxW)
  KBUILD_MODNAME and checkpatch fixes
  KBUILD_MODNAME and checkpatch fixes
  KBUILD_MODNAME instead of "ramster: "

 drivers/staging/zcache/ramster/ramster.c |   34 ++++----
 drivers/staging/zcache/ramster/tcp.c     |   36 ++++----
 drivers/staging/zcache/zbud.c            |    4 +-
 drivers/staging/zcache/zcache-main.c     |  137 ++++++++++++++----------------
 4 files changed, 103 insertions(+), 108 deletions(-)

-- 
1.7.9.5


             reply	other threads:[~2013-02-16  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-16  8:35 Robert Berger [this message]
2013-02-16  8:35 ` [PATCH 1/4] staging/zache checkpatch ERROR: spaces prohibited around that Robert Berger
2013-02-16  8:35 ` [PATCH 2/4] staging/zache BUILD_MODNAME and checkpatch fixes Robert Berger
2013-02-18 18:51   ` Greg KH
2013-02-16  8:35 ` [PATCH 3/4] staging/zache KBUILD_MODNAME " Robert Berger
2013-02-16  8:35 ` [PATCH 4/4] staging/zcache KBUILD_MODNAME instead of "ramster: " Robert Berger

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=1361003754-22512-1-git-send-email-rber.git@ReliableEmbeddedSystems.com \
    --to=git.rber@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=rber.git@ReliableEmbeddedSystems.com \
    --cc=sjenning@linux.vnet.ibm.com \
    --cc=xiaoguangrong@linux.vnet.ibm.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