==========
checkpatch - FAILED

CHECK: Please don't use multiple blank lines
#48: FILE: drivers/net/virtio_net.c:2881:
 
+

ERROR: code indent should use tabs where possible
#157: FILE: drivers/net/virtio_net.c:6589:
+           otherwise get link status from config. */$

WARNING: Block comments use * on subsequent lines
#157: FILE: drivers/net/virtio_net.c:6589:
+	/* Assume link up if device can't report link status,
+           otherwise get link status from config. */

WARNING: Block comments use a trailing */ on a separate line
#157: FILE: drivers/net/virtio_net.c:6589:
+           otherwise get link status from config. */

ERROR: code indent should use tabs where possible
#158: FILE: drivers/net/virtio_net.c:6590:
+        netif_carrier_off(dev);$

WARNING: please, no spaces at the start of a line
#158: FILE: drivers/net/virtio_net.c:6590:
+        netif_carrier_off(dev);$

ERROR: code indent should use tabs where possible
#159: FILE: drivers/net/virtio_net.c:6591:
+        if (virtio_has_feature(vi->vdev, VIRTIO_NET_F_STATUS)) {$

WARNING: please, no spaces at the start of a line
#159: FILE: drivers/net/virtio_net.c:6591:
+        if (virtio_has_feature(vi->vdev, VIRTIO_NET_F_STATUS)) {$

WARNING: Block comments use * on subsequent lines
#161: FILE: drivers/net/virtio_net.c:6593:
+		/* This is safe as config notification change has been
+		   disabled. */

WARNING: Block comments use a trailing */ on a separate line
#161: FILE: drivers/net/virtio_net.c:6593:
+		   disabled. */

ERROR: code indent should use tabs where possible
#162: FILE: drivers/net/virtio_net.c:6594:
+                virtnet_config_changed_work(&vi->config_work);$

WARNING: please, no spaces at the start of a line
#162: FILE: drivers/net/virtio_net.c:6594:
+                virtnet_config_changed_work(&vi->config_work);$

ERROR: code indent should use tabs where possible
#163: FILE: drivers/net/virtio_net.c:6595:
+        } else {$

WARNING: please, no spaces at the start of a line
#163: FILE: drivers/net/virtio_net.c:6595:
+        } else {$

ERROR: code indent should use tabs where possible
#164: FILE: drivers/net/virtio_net.c:6596:
+                vi->status = VIRTIO_NET_S_LINK_UP;$

WARNING: please, no spaces at the start of a line
#164: FILE: drivers/net/virtio_net.c:6596:
+                vi->status = VIRTIO_NET_S_LINK_UP;$

ERROR: code indent should use tabs where possible
#165: FILE: drivers/net/virtio_net.c:6597:
+                virtnet_update_settings(vi);$

WARNING: please, no spaces at the start of a line
#165: FILE: drivers/net/virtio_net.c:6597:
+                virtnet_update_settings(vi);$

ERROR: code indent should use tabs where possible
#166: FILE: drivers/net/virtio_net.c:6598:
+                netif_carrier_on(dev);$

WARNING: please, no spaces at the start of a line
#166: FILE: drivers/net/virtio_net.c:6598:
+                netif_carrier_on(dev);$

ERROR: code indent should use tabs where possible
#167: FILE: drivers/net/virtio_net.c:6599:
+        }$

WARNING: please, no spaces at the start of a line
#167: FILE: drivers/net/virtio_net.c:6599:
+        }$

total: 9 errors, 12 warnings, 1 checks, 138 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

NOTE: Whitespace errors detected.
      You may wish to use scripts/cleanpatch or scripts/cleanfile

Commit 36cd1c124e6a ("virtio-net: synchronize operstate with admin state on up/down") has style problems, please review.

NOTE: Ignored message types: ALLOC_SIZEOF_STRUCT BAD_REPORTED_BY_LINK CAMELCASE COMMIT_LOG_LONG_LINE GIT_COMMIT_ID MACRO_ARG_REUSE NO_AUTHOR_SIGN_OFF

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.