From: Steven Rostedt <rostedt@goodmis.org>
To: Borislav Petkov <bp@alien8.de>
Cc: LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Jason Baron <jbaron@akamai.com>,
trivial@kernel.org
Subject: Re: [PATCH] jump_label: Fix typo in warning message
Date: Fri, 7 Sep 2018 11:19:07 -0400 [thread overview]
Message-ID: <20180907111907.750bbdaf@gandalf.local.home> (raw)
In-Reply-To: <20180907103521.31344-1-bp@alien8.de>
On Fri, 7 Sep 2018 12:35:21 +0200
Borislav Petkov <bp@alien8.de> wrote:
> From: Borislav Petkov <bp@suse.de>
>
> There's no 'allocatote' - use the next best thing: 'allocate' :-)
Nice.
Probably can go through the trivial tree (Cc'd).
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: Josh Poimboeuf <jpoimboe@redhat.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
> Cc: Jason Baron <jbaron@akamai.com>
> ---
> kernel/jump_label.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/jump_label.c b/kernel/jump_label.c
> index 01ebdf1f9f40..2e62503bea0d 100644
> --- a/kernel/jump_label.c
> +++ b/kernel/jump_label.c
> @@ -678,7 +678,7 @@ jump_label_module_notify(struct notifier_block *self, unsigned long val,
> case MODULE_STATE_COMING:
> ret = jump_label_add_module(mod);
> if (ret) {
> - WARN(1, "Failed to allocatote memory: jump_label may not work properly.\n");
> + WARN(1, "Failed to allocate memory: jump_label may not work properly.\n");
> jump_label_del_module(mod);
> }
> break;
next prev parent reply other threads:[~2018-09-07 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 10:35 Borislav Petkov
2018-09-07 11:39 ` Peter Zijlstra
2018-09-07 15:19 ` Steven Rostedt [this message]
2018-09-10 10:08 ` [tip:locking/core] " tip-bot for Borislav Petkov
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=20180907111907.750bbdaf@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bp@alien8.de \
--cc=jbaron@akamai.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=trivial@kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®