linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Parth Y Shah <sparth1292@gmail.com>
To: balbi@kernel.org, gregkh@linuxfoundation.org, linux-usb@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Parth Y Shah <sparth1292@gmail.com>
Subject: [PATCH v2] Fixed a checkpatch error
Date: Thu, 14 Jun 2018 12:02:46 +0530	[thread overview]
Message-ID: <1528957966-24707-1-git-send-email-sparth1292@gmail.com> (raw)
In-Reply-To: <b34abe879f77c55d29ef8a2b1cd9aa0e09ee2a3b.camel@perches.com>

ERROR: code indent should use tabs where possible

Here, spaces are replaced by a tab in 2 lines.

Signed-off-by: Parth Y Shah <sparth1292@gmail.com>
---
Changes since v1:
 * Updated commit description
 * Removed one extra tab and replaced spaces with tab to resolve
   checkpatch error

 drivers/usb/gadget/configfs.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/usb/gadget/configfs.c b/drivers/usb/gadget/configfs.c
index efba66c..0251299 100644
--- a/drivers/usb/gadget/configfs.c
+++ b/drivers/usb/gadget/configfs.c
@@ -1217,8 +1217,8 @@ static void purge_configs_funcs(struct gadget_info *gi)
 			list_move_tail(&f->list, &cfg->func_list);
 			if (f->unbind) {
 				dev_dbg(&gi->cdev.gadget->dev,
-				         "unbind function '%s'/%p\n",
-				         f->name, f);
+					"unbind function '%s'/%p\n",
+					f->name, f);
 				f->unbind(c, f);
 			}
 		}
-- 
2.7.4


  reply	other threads:[~2018-06-14  6:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13 12:25 [PATCH] Fixed an indentation error Parth Y Shah
2018-06-13 12:32 ` Joe Perches
2018-06-14  6:32   ` Parth Y Shah [this message]
2018-06-14  6:42     ` [PATCH v2] Fixed a checkpatch error Greg KH
2018-06-13 12:36 ` [PATCH] Fixed an indentation error 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=1528957966-24707-1-git-send-email-sparth1292@gmail.com \
    --to=sparth1292@gmail.com \
    --cc=balbi@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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).