All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Kyle Moffett <mrmacman_g4@mac.com>, linux-kernel@vger.kernel.org
Subject: Re: Why is kmem_bufctl_t different across platforms?
Date: Mon, 29 Aug 2005 01:37:16 +0200	[thread overview]
Message-ID: <20050828233716.GB3820@stusta.de> (raw)
In-Reply-To: <20050828145503.7b1a5f71.akpm@osdl.org>

On Sun, Aug 28, 2005 at 02:55:03PM -0700, Andrew Morton wrote:
> Kyle Moffett <mrmacman_g4@mac.com> wrote:
> >
> > While exploring the asm-*/types.h files, I discovered that the
> >  type "kmem_bufctl_t" is differently defined across each platform,
> >  sometimes as a short, and sometimes as an int.  The only file
> >  where it's used is mm/slab.c, and as far as I can tell, that file
> >  doesn't care at all, aside from preferring it to be a small-sized
> >  type.
> 
> I don't think there's any good reason for this.  -mm's
> slab-leak-detector.patch switches them all to unsigned long.

What about moving it to include/linux/types.h ?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-08-28 23:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-28 21:42 Why is kmem_bufctl_t different across platforms? Kyle Moffett
2005-08-28 21:55 ` Andrew Morton
2005-08-28 23:37   ` Adrian Bunk [this message]
2005-08-29  2:00     ` Kyle Moffett

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=20050828233716.GB3820@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.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.