From: Rusty Russell <rusty@rustcorp.com.au>
To: Yannick Guerrini <yguerrini@tomshardware.fr>
Cc: linux-kernel@vger.kernel.org,
Yannick Guerrini <yguerrini@tomshardware.fr>
Subject: Re: [PATCH] kernel/module.c: fix typos in message about unused symbols
Date: Wed, 25 Feb 2015 11:14:09 +1030 [thread overview]
Message-ID: <87a902n7l2.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1424476599-11544-1-git-send-email-yguerrini@tomshardware.fr>
Yannick Guerrini <yguerrini@tomshardware.fr> writes:
> Fix typos in pr_warn message about unused symbols
>
> Signed-off-by: Yannick Guerrini <yguerrini@tomshardware.fr>
Thanks. AFAICT you changed "evalute" to "evaluate", "mainlinglist" to
"mailing list" and added a "to".
Applied,
Rusty.
> ---
> kernel/module.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/module.c b/kernel/module.c
> index b34813f..7441733 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -388,9 +388,9 @@ static bool check_symbol(const struct symsearch *syms,
> pr_warn("Symbol %s is marked as UNUSED, however this module is "
> "using it.\n", fsa->name);
> pr_warn("This symbol will go away in the future.\n");
> - pr_warn("Please evalute if this is the right api to use and if "
> - "it really is, submit a report the linux kernel "
> - "mailinglist together with submitting your code for "
> + pr_warn("Please evaluate if this is the right api to use and "
> + "if it really is, submit a report to the linux kernel "
> + "mailing list together with submitting your code for "
> "inclusion.\n");
> }
> #endif
> --
> 1.9.5.msysgit.0
next prev parent reply other threads:[~2015-02-25 4:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 23:56 [PATCH] kernel/module.c: fix typos in message about unused symbols Yannick Guerrini
2015-02-25 0:44 ` Rusty Russell [this message]
2015-02-25 7:33 ` Yannick Guerrini
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=87a902n7l2.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=yguerrini@tomshardware.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.