linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: trivial@kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 9/9] objtool: fix typo 'can by' to 'can be'
Date: Sun,  6 May 2018 13:23:53 +0200	[thread overview]
Message-ID: <20180506112404.24872-10-wsa+renesas@sang-engineering.com> (raw)
In-Reply-To: <20180506112404.24872-1-wsa+renesas@sang-engineering.com>

Signed-off-by: Wolfram Sang <wsa+renesas@sang-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

      parent reply	other threads:[~2018-05-06 11:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-06 11:23 [PATCH 0/9] tree-wide: fix typo 'can by' to 'can be' Wolfram Sang
2018-05-06 11:23 ` [PATCH 1/9] dt-bindings: i2c: " Wolfram Sang
2018-05-10 10:41   ` Wolfram Sang
2018-05-06 11:23 ` [PATCH 2/9] powerpc/watchdog: " Wolfram Sang
2018-05-10 14:06   ` [2/9] " Michael Ellerman
2018-05-06 11:23 ` [PATCH 3/9] base: core: " Wolfram Sang
2018-05-06 11:23 ` [PATCH 4/9] hwmon: fschmd: " Wolfram Sang
2018-05-08  4:42   ` Guenter Roeck
2018-05-06 11:23 ` [PATCH 5/9] input: ati_remote2: " Wolfram Sang
2018-05-08 22:39   ` Dmitry Torokhov
2018-05-06 11:23 ` [PATCH 6/9] NTB: ntb_hw_idt: " Wolfram Sang
2018-05-11 13:12   ` Serge Semin
2018-05-22  0:35     ` Jon Mason
2018-05-06 11:23 ` [PATCH 7/9] reiserfs: journal: " Wolfram Sang
2018-05-06 11:23 ` [PATCH 8/9] net: flow_dissector: " Wolfram Sang
2018-05-08  3:47   ` David Miller
2018-05-06 11:23 ` Wolfram Sang [this message]

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=20180506112404.24872-10-wsa+renesas@sang-engineering.com \
    --to=wsa+renesas@sang-engineering.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=trivial@kernel.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 NNTP newsgroup(s).