[PATCH 5/7] zram/xvmalloc: wrap debug code in #ifdef DEBUG
Robert Jennings
rcj at linux.vnet.ibm.com
Wed Jan 26 18:27:47 UTC 2011
* Pekka Enberg (penberg at kernel.org) wrote:
> On Wed, Jan 26, 2011 at 7:26 PM, Robert Jennings <rcj at linux.vnet.ibm.com> wrote:
> > This wraps the code, noted by comments as being debug code, with
> > #ifdef DEBUG so that it is removed from running in non-debug kernels.
> >
> > Signed-off-by: Robert Jennings <rcj at linux.vnet.ibm.com>
> > ---
> > drivers/staging/zram/xvmalloc.c | 4 +++-
> > 1 files changed, 3 insertions(+), 1 deletions(-)
> >
> > diff --git a/drivers/staging/zram/xvmalloc.c b/drivers/staging/zram/xvmalloc.c
> > index b3622f1..172514e 100644
> > --- a/drivers/staging/zram/xvmalloc.c
> > +++ b/drivers/staging/zram/xvmalloc.c
> > @@ -219,7 +219,6 @@ static void insert_block(struct xv_pool *pool, struct page *page, u32 offset,
> > static void remove_block_head(struct xv_pool *pool,
> > struct block_header *block, u32 slindex)
> > {
> > - struct block_header *tmpblock;
> > u32 flindex = slindex / BITS_PER_LONG;
> >
> > pool->freelist[slindex].page = block->link.next_page;
> > @@ -232,6 +231,8 @@ static void remove_block_head(struct xv_pool *pool,
> > if (!pool->slbitmap[flindex])
> > __clear_bit(flindex, &pool->flbitmap);
> > } else {
> > +#ifdef DEBUG
>
> Shouldn't that be something people can enable from Kconfig?
It should be, I'll correct this and re-post.
More information about the devel
mailing list