From: Hui Tang <tanghui20@huawei.com>
To: <davem@davemloft.net>, <kuba@kernel.org>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Hui Tang <tanghui20@huawei.com>,
Steffen Klassert <klassert@kernel.org>,
Jes Sorensen <jes@trained-monkey.org>,
Michael Chan <michael.chan@broadcom.com>,
"Rasesh Mody" <rmody@marvell.com>, <GR-Linux-NIC-Dev@marvell.com>,
Raju Rangoju <rajur@chelsio.com>,
Denis Kirjanov <kda@linux-powerpc.org>,
Mirko Lindner <mlindner@marvell.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Russell King <linux@armlinux.org.uk>,
Daniele Venzano <venza@brownhat.org>,
Nicolas Pitre <nico@fluxnic.net>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Shannon Nelson <snelson@pensando.io>,
Lee Jones <lee.jones@linaro.org>, "Joe Perches" <joe@perches.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Weihang Li <liweihang@huawei.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Yixing Liu <liuyixing1@huawei.com>,
"Vaibhav Gupta" <vaibhavgupta40@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Miguel Ojeda <ojeda@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>, Jeremy Kerr <jk@ozlabs.org>,
Moritz Fischer <mdf@kernel.org>, Lucy Yan <lucyyan@google.com>,
Wei Yongjun <weiyongjun1@huawei.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Edward Cree <ecree@solarflare.com>,
Zheng Yongjun <zhengyongjun3@huawei.com>,
Jason Yan <yanaijie@huawei.com>, Andrew Lunn <andrew@lunn.ch>,
Colin Ian King <colin.king@canonical.com>,
Romain Perier <romain.perier@gmail.com>,
"Allen Pais" <apais@linux.microsoft.com>,
Luo Jiaxing <luojiaxing@huawei.com>,
"Wang Hai" <wanghai38@huawei.com>, Qiushi Wu <wu000273@umn.edu>,
Kees Cook <keescook@chromium.org>,
Bhaskar Chowdhury <unixbhaskar@gmail.com>,
YueHaibing <yuehaibing@huawei.com>,
Gaurav Singh <gaurav1086@gmail.com>, <linux-acenic@sunsite.dk>,
<linux-parisc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 01/20] net: 3com: remove leading spaces before tabs
Date: Wed, 19 May 2021 12:45:26 +0800 [thread overview]
Message-ID: <1621399671-15517-2-git-send-email-tanghui20@huawei.com> (raw)
In-Reply-To: <1621399671-15517-1-git-send-email-tanghui20@huawei.com>
There are a few leading space before tabs and remove it by running the
following commard:
$ find . -name '*.c' | xargs sed -r -i 's/^[ ]+\t/\t/'
$ find . -name '*.h' | xargs sed -r -i 's/^[ ]+\t/\t/'
Signed-off-by: Hui Tang <tanghui20@huawei.com>
---
drivers/net/ethernet/3com/3c59x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/3com/3c59x.c b/drivers/net/ethernet/3com/3c59x.c
index 741c67e..7d7d3ff 100644
--- a/drivers/net/ethernet/3com/3c59x.c
+++ b/drivers/net/ethernet/3com/3c59x.c
@@ -1464,7 +1464,7 @@ static int vortex_probe1(struct device *gendev, void __iomem *ioaddr, int irq,
if (pdev) {
vp->pm_state_valid = 1;
pci_save_state(pdev);
- acpi_set_WOL(dev);
+ acpi_set_WOL(dev);
}
retval = register_netdev(dev);
if (retval == 0)
--
2.8.1
next prev parent reply other threads:[~2021-05-19 4:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 4:45 [PATCH 00/20] net: ethernet: remove leading spaces before tabs Hui Tang
2021-05-19 4:45 ` Hui Tang [this message]
2021-05-19 4:45 ` [PATCH 02/20] net: alteon: " Hui Tang
2021-05-19 4:45 ` [PATCH 03/20] net: amd: " Hui Tang
2021-05-19 4:45 ` [PATCH 04/20] net: apple: " Hui Tang
2021-05-19 4:45 ` [PATCH 05/20] net: broadcom: " Hui Tang
2021-05-19 5:04 ` [PATCH 00/20] net: ethernet: " Hui Tang
2021-05-19 5:30 Hui Tang
2021-05-19 5:30 ` [PATCH 01/20] net: 3com: " Hui Tang
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=1621399671-15517-2-git-send-email-tanghui20@huawei.com \
--to=tanghui20@huawei.com \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=akpm@linux-foundation.org \
--cc=andrew@lunn.ch \
--cc=apais@linux.microsoft.com \
--cc=bigeasy@linutronix.de \
--cc=christophe.jaillet@wanadoo.fr \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=gaurav1086@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gustavoars@kernel.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jes@trained-monkey.org \
--cc=jesse.brandeburg@intel.com \
--cc=jk@ozlabs.org \
--cc=joe@perches.com \
--cc=kda@linux-powerpc.org \
--cc=keescook@chromium.org \
--cc=klassert@kernel.org \
--cc=kuba@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-acenic@sunsite.dk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=liuyixing1@huawei.com \
--cc=liweihang@huawei.com \
--cc=lucyyan@google.com \
--cc=luojiaxing@huawei.com \
--cc=masahiroy@kernel.org \
--cc=mdf@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=mlindner@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=ojeda@kernel.org \
--cc=rajur@chelsio.com \
--cc=rmody@marvell.com \
--cc=romain.perier@gmail.com \
--cc=rppt@kernel.org \
--cc=snelson@pensando.io \
--cc=stephen@networkplumber.org \
--cc=tglx@linutronix.de \
--cc=unixbhaskar@gmail.com \
--cc=vaibhavgupta40@gmail.com \
--cc=venza@brownhat.org \
--cc=wanghai38@huawei.com \
--cc=weiyongjun1@huawei.com \
--cc=wu000273@umn.edu \
--cc=yanaijie@huawei.com \
--cc=yuehaibing@huawei.com \
--cc=zhengyongjun3@huawei.com \
/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).