From: Vivien Didelot <vivien.didelot@gmail.com>
To: barebox@lists.infradead.org
Cc: Vivien Didelot <vdidelot@pbsc.com>
Subject: [PATCH] Documentation: fix sucessfuly -> successfully typo
Date: Tue, 6 Apr 2021 11:01:20 -0400 [thread overview]
Message-ID: <20210406150120.4194149-1-vivien.didelot@gmail.com> (raw)
From: Vivien Didelot <vdidelot@pbsc.com>
system-reset.rst was embedded a classic sucess -> success typo. Fix it.
Signed-off-by: Vivien Didelot <vdidelot@pbsc.com>
---
Documentation/user/system-reset.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/user/system-reset.rst b/Documentation/user/system-reset.rst
index e76e3a23c1..bf7369d06f 100644
--- a/Documentation/user/system-reset.rst
+++ b/Documentation/user/system-reset.rst
@@ -31,7 +31,7 @@ But there are some drawbacks within this simple approach.
* some SoC's boot behaviour gets parametrized by so called 'bootstrap pins'.
These pins can have a different meaning at reset time and at run-time later
on (multi purpose pins) but their correct values at reset time are very
- important to boot the SoC sucessfully. If external devices are connected to
+ important to boot the SoC successfully. If external devices are connected to
these multi purpose pins they can disturb the reset values, and so parametrizing
the boot behaviour differently and hence crashing the SoC until the next real
POR happens which also resets the external devices (and keep them away from the
--
2.30.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
reply other threads:[~2021-04-06 15:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210406150120.4194149-1-vivien.didelot@gmail.com \
--to=vivien.didelot@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=vdidelot@pbsc.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