From: Cheng-Yang Chou <yphbchou0911@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, corbet@lwn.net, jserv@ccns.ncku.edu.tw,
mingo@elte.hu, peterz@infradead.org,
Cheng-Yang Chou <yphbchou0911@gmail.com>
Subject: [PATCH v2] genirq: Fix typo in IRQ_NOTCONNECTED comment
Date: Thu, 10 Apr 2025 18:51:43 +0800 [thread overview]
Message-ID: <20250410105144.214849-1-yphbchou0911@gmail.com> (raw)
In-Reply-To: <87bjt4tnjz.ffs@tglx>
Fix a minor typo in the comment for IRQ_NOTCONNECTED definition:
"distingiush" is corrected to "distinguish".
Signed-off-by: Cheng-Yang Chou <yphbchou0911@gmail.com>
---
include/linux/interrupt.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h
index c782a74d2a30..51b6484c0493 100644
--- a/include/linux/interrupt.h
+++ b/include/linux/interrupt.h
@@ -140,7 +140,7 @@ extern irqreturn_t no_action(int cpl, void *dev_id);
/*
* If a (PCI) device interrupt is not connected we set dev->irq to
* IRQ_NOTCONNECTED. This causes request_irq() to fail with -ENOTCONN, so we
- * can distingiush that case from other error returns.
+ * can distinguish that case from other error returns.
*
* 0x80000000 is guaranteed to be outside the available range of interrupts
* and easy to distinguish from other possible incorrect values.
base-commit: 92b71befc349587d58fdbbe6cdd68fb67f4933a8
--
2.43.0
next prev parent reply other threads:[~2025-04-10 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 7:39 [PATCH] IRQ_NOTCONNECTED: fix typo in comment Cheng-Yang Chou
2025-04-10 8:42 ` Thomas Gleixner
2025-04-10 10:51 ` Cheng-Yang Chou [this message]
2025-04-10 14:57 ` [tip: timers/core] genirq: Fix typo in IRQ_NOTCONNECTED comment tip-bot2 for Cheng-Yang Chou
2025-04-24 12:39 ` [tip: irq/core] " tip-bot2 for Cheng-Yang Chou
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=20250410105144.214849-1-yphbchou0911@gmail.com \
--to=yphbchou0911@gmail.com \
--cc=corbet@lwn.net \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®