From: Tal Shorer <tal.shorer@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: oleg.drokin@intel.com, devel@driverdev.osuosl.org,
andreas.dilger@intel.com, gregkh@linuxfoundation.org,
clabbe.montjoie@gmail.com, dan.carpenter@oracle.com,
tal.shorer@gmail.com
Subject: [PATCH v4 3/3] staging: lustre: fix coding style errors fix the
Date: Tue, 10 Feb 2015 20:36:21 +0200 [thread overview]
Message-ID: <1423593381-10452-3-git-send-email-tal.shorer@gmail.com> (raw)
In-Reply-To: <1423593381-10452-1-git-send-email-tal.shorer@gmail.com>
following coding style error in drivers/staging/lustre/lustre/libcfs/linux/linux-proc.c:
missing spaces around '='
Signed-off-by: Tal Shorer <tal.shorer@gmail.com>
---
drivers/staging/lustre/lustre/libcfs/linux/linux-proc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/libcfs/linux/linux-proc.c b/drivers/staging/lustre/lustre/libcfs/linux/linux-proc.c
index c3d00e6..d70330f 100644
--- a/drivers/staging/lustre/lustre/libcfs/linux/linux-proc.c
+++ b/drivers/staging/lustre/lustre/libcfs/linux/linux-proc.c
@@ -308,7 +308,7 @@ static int proc_console_backoff(struct ctl_table *table, int write,
dummy.proc_handler = &proc_dointvec;
if (!write) { /* read */
- backoff= libcfs_console_backoff;
+ backoff = libcfs_console_backoff;
rc = proc_dointvec(&dummy, write, buffer, lenp, ppos);
return rc;
}
--
2.2.2
next prev parent reply other threads:[~2015-02-10 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 18:36 [PATCH v4 1/3] staging: lustre: fix coding style errors Tal Shorer
2015-02-10 18:36 ` [PATCH v4 2/3] " Tal Shorer
2015-03-02 1:28 ` Greg KH
2015-02-10 18:36 ` Tal Shorer [this message]
2015-03-02 1:27 ` [PATCH v4 3/3] staging: lustre: fix coding style errors fix the Greg KH
2015-03-02 1:27 ` [PATCH v4 1/3] staging: lustre: fix coding style errors 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=1423593381-10452-3-git-send-email-tal.shorer@gmail.com \
--to=tal.shorer@gmail.com \
--cc=andreas.dilger@intel.com \
--cc=clabbe.montjoie@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®