linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pranay Kr. Srivastava" <pranjas@gmail.com>
To: gregkh@linuxfoundation.org, mpa@pengutronix.de,
	nbd-general@lists.sourceforge.net, linux-kernel@vger.kernel.org
Cc: "Pranay Kr. Srivastava" <pranjas@gmail.com>
Subject: [PATCH v3 08/17] nbd : fix checkpatch line over 80 char warning
Date: Fri,  6 May 2016 11:49:32 +0300	[thread overview]
Message-ID: <1462524581-9790-9-git-send-email-pranjas@gmail.com> (raw)
In-Reply-To: <1462524581-9790-1-git-send-email-pranjas@gmail.com>

Signed-off-by: Pranay Kr. Srivastava <pranjas@gmail.com>
---
 drivers/block/nbd.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
index 7a5b8ef..224b44eb 100644
--- a/drivers/block/nbd.c
+++ b/drivers/block/nbd.c
@@ -617,8 +617,8 @@ static int nbd_thread_send(void *data)
 }
 
 /*
- * We always wait for result of write, for now. It would be nice to make it optional
- * in future
+ * We always wait for result of write, for now. It would be nice to make it
+ * optional in future
  * if ((rq_data_dir(req) == WRITE) && (nbd->flags & NBD_WRITE_NOCHK))
  *   { printk( "Warning: Ignoring result!\n"); nbd_end_request( req ); }
  */
-- 
2.6.2

  parent reply	other threads:[~2016-05-06  8:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-06  8:49 [PATCH v3 00/17] nbd : fix might sleep warning and checkpatch errors Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 01/17] nbd: Fix might_sleep warning on xmit timeout Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 02/17] nbd: fix checkpatch trailing space warning Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 03/17] nbd: fix checkpatch warning use linux/uaccess.h Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 04/17] nbd : fix checkpatch pointer declaration warning Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 05/17] nbd: fix checkpatch warning no newline after decleration Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 06/17] " Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 07/17] nbd: fix checkpatch split string warning Pranay Kr. Srivastava
2016-05-06  8:49 ` Pranay Kr. Srivastava [this message]
2016-05-06  8:49 ` [PATCH v3 09/17] nbd: fix checkpatch trailing whitespace warning Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 10/17] " Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 11/17] nbd : fix checkpatch structure declaration braces on next line warning Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 12/17] nbd : fix checkpatch trailing whitespace warning Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 13/17] nbd : fix checkpatch printk warning Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 14/17] nbd: fix checkpatch no extra line after decleration warning Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 15/17] nbd: fix checkpatch printk warning to pr_info Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 16/17] nbd: fix checkpatch no new line after decleration warning Pranay Kr. Srivastava
2016-05-06  8:49 ` [PATCH v3 17/17] nbd: fix checkpatch printk warning to pr_info Pranay Kr. Srivastava

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=1462524581-9790-9-git-send-email-pranjas@gmail.com \
    --to=pranjas@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpa@pengutronix.de \
    --cc=nbd-general@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).