[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180506112404.24872-10-wsa+renesas@sang-engineering.com>
Date: Sun, 6 May 2018 13:23:53 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: trivial@...nel.org
Cc: linux-renesas-soc@...r.kernel.org,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
linux-kernel@...r.kernel.org
Subject: [PATCH 9/9] objtool: fix typo 'can by' to 'can be'
Signed-off-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
---
tools/objtool/Documentation/stack-validation.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/objtool/Documentation/stack-validation.txt b/tools/objtool/Documentation/stack-validation.txt
index 3995735a878fe7..b8a32534b9d5de 100644
--- a/tools/objtool/Documentation/stack-validation.txt
+++ b/tools/objtool/Documentation/stack-validation.txt
@@ -136,7 +136,7 @@ To achieve the validation, objtool enforces the following rules:
3. Each callable function which calls another function must have the
correct frame pointer logic, if required by CONFIG_FRAME_POINTER or
- the architecture's back chain rules. This can by done in asm code
+ the architecture's back chain rules. This can be done in asm code
with the FRAME_BEGIN/FRAME_END macros.
This rule ensures that frame pointer based stack traces will work as
--
2.11.0
Powered by blists - more mailing lists