public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Maciek Fijalkowski <macfij7@wp.pl>
To: mst@redhat.com
Cc: jasonwang@redhat.com, virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Maciej Fijalkowski <macfij7@wp.pl>
Subject: [PATCH 3/3] Fix ERROR: code indent should use tabs where possible
Date: Sun, 14 May 2017 19:51:30 +0200	[thread overview]
Message-ID: <20170514175130.18664-3-macfij7@wp.pl> (raw)
In-Reply-To: <20170514175130.18664-1-macfij7@wp.pl>

From: Maciej Fijalkowski <macfij7@wp.pl>

Signed-off-by: Maciej Fijalkowski <macfij7@wp.pl>
---
 drivers/net/virtio_net.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
index 6c8170c..5d71e9f 100644
--- a/drivers/net/virtio_net.c
+++ b/drivers/net/virtio_net.c
@@ -2717,7 +2717,7 @@ static __init int virtio_net_driver_init(void)
 	if (ret)
 		goto err_dead;
 
-        ret = register_virtio_driver(&virtio_net_driver);
+	ret = register_virtio_driver(&virtio_net_driver);
 	if (ret)
 		goto err_virtio;
 	return 0;
-- 
2.4.11

  parent reply	other threads:[~2017-05-14 17:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-14 17:51 [PATCH 1/3] Fix ERROR: trailing statements should be on next line Maciek Fijalkowski
2017-05-14 17:51 ` [PATCH 2/3] Fix ERROR: Macros with complex values should be enclosed in parentheses Maciek Fijalkowski
2017-05-14 18:48   ` kbuild test robot
2017-05-15  0:25   ` Andrew Lunn
2017-05-15  2:56   ` Michael S. Tsirkin
2017-05-14 17:51 ` Maciek Fijalkowski [this message]
2017-05-15  3:00   ` [PATCH 3/3] Fix ERROR: code indent should use tabs where possible Michael S. Tsirkin
2017-05-15  2:58 ` [PATCH 1/3] Fix ERROR: trailing statements should be on next line Michael S. Tsirkin
2017-05-15  3:20   ` Alex Williamson
2017-05-15 14:25     ` David Laight

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=20170514175130.18664-3-macfij7@wp.pl \
    --to=macfij7@wp.pl \
    --cc=jasonwang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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