ERROR: trailing whitespace
#30: FILE: drivers/net/ethernet/broadcom/b44.c:967:
+    $

WARNING: please, no spaces at the start of a line
#30: FILE: drivers/net/ethernet/broadcom/b44.c:967:
+    $

WARNING: please, no spaces at the start of a line
#31: FILE: drivers/net/ethernet/broadcom/b44.c:968:
+    if (dma_mapping_error(bp->sdev->dma_dev, mapping)) {$

ERROR: code indent should use tabs where possible
#32: FILE: drivers/net/ethernet/broadcom/b44.c:969:
+        dev_kfree_skb_any(skb);$

WARNING: please, no spaces at the start of a line
#32: FILE: drivers/net/ethernet/broadcom/b44.c:969:
+        dev_kfree_skb_any(skb);$

ERROR: code indent should use tabs where possible
#33: FILE: drivers/net/ethernet/broadcom/b44.c:970:
+        return NETDEV_TX_OK;$

WARNING: please, no spaces at the start of a line
#33: FILE: drivers/net/ethernet/broadcom/b44.c:970:
+        return NETDEV_TX_OK;$

WARNING: please, no spaces at the start of a line
#34: FILE: drivers/net/ethernet/broadcom/b44.c:971:
+    }$

WARNING: please, no spaces at the start of a line
#36: FILE: drivers/net/ethernet/broadcom/b44.c:973:
+    if (mapping + len > DMA_BIT_MASK(30)) {$

ERROR: code indent should use tabs where possible
#37: FILE: drivers/net/ethernet/broadcom/b44.c:974:
+        struct sk_buff *bounce_skb;$

WARNING: please, no spaces at the start of a line
#37: FILE: drivers/net/ethernet/broadcom/b44.c:974:
+        struct sk_buff *bounce_skb;$

total: 4 errors, 7 warnings, 0 checks, 16 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 63a6aa3850e8 ("net: broadcom: b44: Add missing dma_mapping_error in b44_start_xmit") has style problems, please review.

NOTE: Ignored message types: ALLOC_SIZEOF_STRUCT BAD_REPORTED_BY_LINK CAMELCASE COMMIT_LOG_LONG_LINE FILE_PATH_CHANGES 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.