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] [thread-next>] [day] [month] [year] [list]
Message-ID: <1357754254.1800.2.camel@buesod1.americas.hpqcorp.net>
Date:	Wed, 09 Jan 2013 09:57:34 -0800
From:	Davidlohr Bueso <davidlohr.bueso@...com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org, Nitin Gupta <ngupta@...are.org>
Subject: Re: [PATCH] staging: zsmalloc: comment zs_create_pool function

ping?

On Fri, 2013-01-04 at 12:14 -0800, Davidlohr Bueso wrote:
> Just as with zs_malloc() and zs_map_object(), it is worth
> formally commenting the zs_create_pool() function.
> 
> Signed-off-by: Davidlohr Bueso <davidlohr.bueso@...com>
> ---
>  drivers/staging/zsmalloc/zsmalloc-main.c | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/drivers/staging/zsmalloc/zsmalloc-main.c b/drivers/staging/zsmalloc/zsmalloc-main.c
> index 09a9d35..eb00772 100644
> --- a/drivers/staging/zsmalloc/zsmalloc-main.c
> +++ b/drivers/staging/zsmalloc/zsmalloc-main.c
> @@ -798,6 +798,17 @@ fail:
>  	return notifier_to_errno(ret);
>  }
>  
> +/**
> + * zs_create_pool - Creates an allocation pool to work from.
> + * @name: name of the pool to be created
> + * @flags: allocation flags used when growing pool
> + *
> + * This function must be called before anything when using
> + * the zsmalloc allocator.
> + *
> + * On success, a pointer to the newly created pool is returned,
> + * otherwise NULL.
> + */
>  struct zs_pool *zs_create_pool(const char *name, gfp_t flags)
>  {
>  	int i, ovhd_size;


--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ