From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jake Champlin <jake.champlin.27@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
sjening@linux.vnet.ibm.com, konrad.wilk@oracle.com,
linux-kernel@vger.kernel.org, xiaoguangrong@linux.vnet.ibm.com,
dan.magenheimer@oracle.com
Subject: Re: [PATCH] Staging: zcache-main: Fixed Camel Case Issue
Date: Sat, 19 Jan 2013 13:53:14 +0300 [thread overview]
Message-ID: <20130119105314.GN4584@mwanda> (raw)
In-Reply-To: <20130119025640.GA32271@gmail.com>
On Fri, Jan 18, 2013 at 09:56:44PM -0500, Jake Champlin wrote:
> Fixed a camel case coding style issue.
>
Stop. It's not OK to break the build.
regards,
dan carpenter
prev parent reply other threads:[~2013-01-19 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 2:56 [PATCH] Staging: zcache-main: Fixed Camel Case Issue Jake Champlin
2013-01-19 3:08 ` Cong Ding
2013-01-19 10:53 ` Dan Carpenter [this message]
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=20130119105314.GN4584@mwanda \
--to=dan.carpenter@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jake.champlin.27@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sjening@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