[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210607063307.376988-1-13145886936@163.com>
Date: Sun, 6 Jun 2021 23:33:07 -0700
From: 13145886936@....com
To: davem@...emloft.net, kuba@...nel.org
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
gushengxian <gushengxian@...ong.com>
Subject: [PATCH] atm: [br2864] fix spelling mistakes
From: gushengxian <gushengxian@...ong.com>
interrupt should be changed to interrupting.
Signed-off-by: gushengxian <gushengxian@...ong.com>
---
net/atm/br2684.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/net/atm/br2684.c b/net/atm/br2684.c
index 3e17a5ecaa94..dd2a8dabed84 100644
--- a/net/atm/br2684.c
+++ b/net/atm/br2684.c
@@ -93,8 +93,8 @@ struct br2684_dev {
* This lock should be held for writing any time the list of devices or
* their attached vcc's could be altered. It should be held for reading
* any time these are being queried. Note that we sometimes need to
- * do read-locking under interrupt context, so write locking must block
- * the current CPU's interrupts
+ * do read-locking under interrupting context, so write locking must block
+ * the current CPU's interrupts.
*/
static DEFINE_RWLOCK(devs_lock);
--
2.25.1
Powered by blists - more mailing lists