From: "Bolivar, Marti" <Marti.Bolivar-hR+23Fw+YnFSHonuZl5R5Q@public.gmane.org>
To: "devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: "Bolivar, Marti" <Marti.Bolivar-hR+23Fw+YnFSHonuZl5R5Q@public.gmane.org>
Subject: [PATCH] Fix missing article
Date: Fri, 7 Feb 2020 22:00:27 +0000 [thread overview]
Message-ID: <20200207220021.437090-1-marti.bolivar@nordicsemi.no> (raw)
s/is physical device/is a physical device/
Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
---
No worries if typo patches aren't welcome; I'm only bothering
since this is spec, not code.
source/devicetree-basics.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/devicetree-basics.rst b/source/devicetree-basics.rst
index b91b048..01b1958 100644
--- a/source/devicetree-basics.rst
+++ b/source/devicetree-basics.rst
@@ -869,7 +869,7 @@ An interrupt domain is the context in which an interrupt specifier is
interpreted. The root of the domain is either (1) an interrupt
controller or (2) an interrupt nexus.
-#. An *interrupt controller* is physical device and will need a driver
+#. An *interrupt controller* is a physical device and will need a driver
to handle interrupts routed through it. It may also cascade into
another interrupt domain. An interrupt controller is specified by the
presence of an *interrupt-controller* property on that node in the
--
2.25.0
next reply other threads:[~2020-02-07 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 22:00 Bolivar, Marti [this message]
[not found] ` <20200207220021.437090-1-marti.bolivar-hR+23Fw+YnFSHonuZl5R5Q@public.gmane.org>
2020-02-13 15:37 ` [PATCH] Fix missing article Rob Herring
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=20200207220021.437090-1-marti.bolivar@nordicsemi.no \
--to=marti.bolivar-hr+23fw+ynfshonuzl5r5q@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).