From: Joe Perches <joe@perches.com>
To: Swee Hua Law <sweehua81@gmail.com>
Cc: andreas.dilger@intel.com, gregkh@linuxfoundation.org,
Julia.Lawall@lip6.fr, hamohammed.sa@gmail.com,
asaf.vertz@tandemg.com, viro@zeniv.linux.org.uk,
HPDD-discuss@ml01.01.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] staging: lustre: Remove the space before \n
Date: Tue, 11 Aug 2015 07:00:34 -0700 [thread overview]
Message-ID: <1439301634.3244.2.camel@perches.com> (raw)
In-Reply-To: <1439299951-2012-4-git-send-email-sweehua81@gmail.com>
On Tue, 2015-08-11 at 21:32 +0800, Swee Hua Law wrote:
> Remove the extra space character right before \n in the string
[]
> diff --git a/drivers/staging/lustre/lustre/llite/lloop.c b/drivers/staging/lustre/lustre/llite/lloop.c
[]
> @@ -308,7 +308,7 @@ static unsigned int loop_get_bio(struct lloop_device *lo, struct bio **req)
> rw = first->bi_rw;
> bio = &lo->lo_bio;
> while (*bio && (*bio)->bi_rw == rw) {
> - CDEBUG(D_INFO, "bio sector %llu size %u count %u vcnt%u \n",
> + CDEBUG(D_INFO, "bio sector %llu size %u count %u vcnt%u\n",
More likely the space is misplaced and it should be:
CDEBUG(D_INFO, "bio sector %llu size %u count %u vcnt %u\n"
prev parent reply other threads:[~2015-08-11 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 13:32 [PATCH 0/3] staging: lustre: fix checkpatch problems in llite/lloop.c Swee Hua Law
2015-08-11 13:32 ` [PATCH 1/3] staging: lustre: Do not init global to NULL Swee Hua Law
2015-08-11 13:32 ` [PATCH 2/3] staging: lustre: Add blank line after variable declaration Swee Hua Law
2015-08-12 5:00 ` Sudip Mukherjee
2015-08-12 6:31 ` Joe Perches
2015-08-11 13:32 ` [PATCH 3/3] staging: lustre: Remove the space before \n Swee Hua Law
2015-08-11 14:00 ` Joe Perches [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=1439301634.3244.2.camel@perches.com \
--to=joe@perches.com \
--cc=HPDD-discuss@ml01.01.org \
--cc=Julia.Lawall@lip6.fr \
--cc=andreas.dilger@intel.com \
--cc=asaf.vertz@tandemg.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sweehua81@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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