linux-kernel - Re: [PATCH] x86/tools/relocs: comments cleanup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 16 Apr 2018 13:59:25 +0800
From:   Cao jin <caoj.fnst@...fujitsu.com>
To:     <linux-kernel@...r.kernel.org>, <x86@...nel.org>
CC:     <tglx@...utronix.de>, <mingo@...hat.com>, <hpa@...or.com>
Subject: Re: [PATCH] x86/tools/relocs: comments cleanup

ping?

On 03/05/2018 03:15 PM, Cao jin wrote:
> 1. typo fix: there -> their
> 2. remove superfluous "by"
> 
> Signed-off-by: Cao jin <caoj.fnst@...fujitsu.com>
> ---
>  arch/x86/tools/relocs.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/x86/tools/relocs.c b/arch/x86/tools/relocs.c
> index 5d73c443e778..fcf3fad01b08 100644
> --- a/arch/x86/tools/relocs.c
> +++ b/arch/x86/tools/relocs.c
> @@ -37,7 +37,7 @@ static struct section *secs;
>  
>  static const char * const sym_regex_kernel[S_NSYMTYPES] = {
>  /*
> - * Following symbols have been audited. There values are constant and do
> + * Following symbols have been audited. Their values are constant and do
>   * not change if bzImage is loaded at a different physical address than
>   * the address for which it has been compiled. Don't warn user about
>   * absolute relocations present w.r.t these symbols.
> @@ -690,7 +690,7 @@ static void walk_relocs(int (*process)(struct section *sec, Elf_Rel *rel,
>   *	to the start of the per_cpu area that does not change).
>   *
>   *	Relocations that apply to the per_cpu area need to have their
> - *	offset adjusted by by the value of __per_cpu_load to make them
> + *	offset adjusted by the value of __per_cpu_load to make them
>   *	point to the correct place in the loaded image (because the
>   *	virtual address of .data..percpu is 0).
>   *
> 

-- 
Sincerely,
Cao jin