From: Raphael Norwitz <raphael.norwitz@nutanix.com>
To: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: raphael.s.norwitz@gmail.com,
Raphael Norwitz <raphael.norwitz@nutanix.com>,
Marc Zyngier <maz@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH] Fix typo in irq_domain documentation
Date: Wed, 19 Aug 2020 21:53:09 +0000 (UTC) [thread overview]
Message-ID: <1597873980-204052-1-git-send-email-raphael.norwitz@nutanix.com> (raw)
The irq_domain documentation states that "Here the interrupt number
loose all kind of correspondence to hardware interrupt numbers:...".
It's clear from the context that the author means to use "loses" instead
of "loose". To avoid future confusion, this change fixes the
aforementioned wording.
Signed-off-by: Raphael Norwitz <raphael.norwitz@nutanix.com>
---
Documentation/core-api/irq/irq-domain.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/core-api/irq/irq-domain.rst b/Documentation/core-api/irq/irq-domain.rst
index 096db12..eba5e41 100644
--- a/Documentation/core-api/irq/irq-domain.rst
+++ b/Documentation/core-api/irq/irq-domain.rst
@@ -15,7 +15,7 @@ such as GPIO controllers avoid reimplementing identical callback
mechanisms as the IRQ core system by modelling their interrupt
handlers as irqchips, i.e. in effect cascading interrupt controllers.
-Here the interrupt number loose all kind of correspondence to
+Here the interrupt number loses all kind of correspondence to
hardware interrupt numbers: whereas in the past, IRQ numbers could
be chosen so they matched the hardware IRQ line into the root
interrupt controller (i.e. the component actually fireing the
--
2.9.3
next reply other threads:[~2020-08-19 21:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 21:53 Raphael Norwitz [this message]
2020-08-25 10:23 ` Marc Zyngier
2020-10-28 2:24 ` Raphael Norwitz
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=1597873980-204052-1-git-send-email-raphael.norwitz@nutanix.com \
--to=raphael.norwitz@nutanix.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=raphael.s.norwitz@gmail.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
all inboxes | Powered by JetHome®