From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: Remove SLAB_CTOR_CONSTRUCTOR
Date: Fri, 11 May 2007 11:27:50 -0700 [thread overview]
Message-ID: <20070511112750.9a9a2b57.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705111105180.22949@schroedinger.engr.sgi.com>
On Fri, 11 May 2007 11:06:41 -0700 (PDT)
Christoph Lameter <clameter@sgi.com> wrote:
> SLAB_CTOR_CONSTRUCTOR is always specified. No point in checking it.
>
> [Sorry Andrew, another one of these "touch lots of kernel files" patch. Defer
> if its not convenient.]
>
> While we are at it: Fix bug in mtd/ubi/eba.c. Check was inverted.
hm. I think what we do here is to merge all the bits which don't conflict
with anyone else's pending work. That means that there will be a few
stragglers left over for a while which we'll need to clean up later on.
next prev parent reply other threads:[~2007-05-11 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 18:06 Remove SLAB_CTOR_CONSTRUCTOR Christoph Lameter
2007-05-11 18:27 ` Andrew Morton [this message]
2007-05-11 18:34 ` Artem Bityutskiy
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=20070511112750.9a9a2b57.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox