All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Kevin Corry <corryk@us.ibm.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
	evms-devel@lists.sourceforge.net
Subject: Re: [PATCH] EVMS core 4/4: evms_biosplit.h
Date: Thu, 3 Oct 2002 16:05:07 +0100	[thread overview]
Message-ID: <20021003160507.A20553@infradead.org> (raw)
In-Reply-To: <02100307382404.05904@boiler>; from corryk@us.ibm.com on Thu, Oct 03, 2002 at 07:38:24AM -0500

> +static mempool_t *my_bio_split_pool, *my_bio_pool;
> +static kmem_cache_t *my_bio_split_slab, *my_bio_pool_slab;

Umm, static variables in header files?

> +
> +/**
> + * slab_pool_alloc
> + * @gfp_mask:	GFP allocation flag
> + * @data:	mempool prototype required fields
> + *
> + * mempool allocate function
> + **/
> +static void *
> +slab_pool_alloc(int gfp_mask, void *data)
> +{
> +	return kmem_cache_alloc(data, gfp_mask);
> +}
> +
> +/**
> + * slab_pool_free
> + * @ptr:	mempool prototype required fields
> + * @data:	mempool prototype required fields
> + *
> + * mempool free function
> + **/
> +static void
> +slab_pool_free(void *ptr, void *data)
> +{
> +	kmem_cache_free(data, ptr);
> +}

I think these two could go to slab.c instead.

> +	if (!my_bio_split_slab) {
> +		panic("unable to create EVMS Bio Split cache.");

What about graceful error handling?

All in all I think this should rather be a source file, I can't
see anything EVMS-specific either.

      parent reply	other threads:[~2002-10-03 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 12:38 [PATCH] EVMS core 4/4: evms_biosplit.h Kevin Corry
2002-10-03 13:57 ` Alan Cox
2002-10-03 15:05 ` Christoph Hellwig [this message]

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=20021003160507.A20553@infradead.org \
    --to=hch@infradead.org \
    --cc=corryk@us.ibm.com \
    --cc=evms-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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.