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:	Sun, 31 Jan 2010 15:53:39 +0900
From:	Akinobu Mita <akinobu.mita@...il.com>
To:	Anton Blanchard <anton@...ba.org>
Cc:	Greg Kroah-Hartman <gregkh@...e.de>, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org
Subject: Re: [PATCH] fault injection: Correct function names in documentation

2010/1/31 Anton Blanchard <anton@...ba.org>:
>
> init_fault_attr_entries should be init_fault_attr_dentries
> cleanup_fault_attr_entries should be cleanup_fault_attr_dentries
>
> Signed-off-by: Anton Blanchard <anton@...ba.org>
> ---
>
> Index: linux-cpumask/Documentation/fault-injection/fault-injection.txt
> ===================================================================
> --- linux-cpumask.orig/Documentation/fault-injection/fault-injection.txt        2010-01-30 17:20:54.147210801 +1100
> +++ linux-cpumask/Documentation/fault-injection/fault-injection.txt     2010-01-31 17:11:10.737211232 +1100
> @@ -143,8 +143,8 @@ o provide a way to configure fault attri
>   failslab, fail_page_alloc, and fail_make_request use this way.
>   Helper functions:
>
> -       init_fault_attr_entries(entries, attr, name);
> -       void cleanup_fault_attr_entries(entries);
> +       init_fault_attr_dentries(entries, attr, name);
> +       void cleanup_fault_attr_dentries(entries);
>
>  - module parameters
>
>

Looks good.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists