From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org
Subject: Re: Slab API: Remove useless ctor parameter and reorder parameters
Date: Wed, 25 Jul 2007 13:33:55 +0300 [thread overview]
Message-ID: <84144f020707250333gc1c2f01l24c7b9ff6211a489@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707242009080.3583@schroedinger.engr.sgi.com>
On 7/25/07, Christoph Lameter <clameter@sgi.com> wrote:
> Yes I thought that to be the appropriate time for such things too and I
> wanted to keep things the way they were until 2.6.24. But that no longer
> seems to be the case. The destructor patch was only merged a few days ago
> and it already breaks my other slab patches that I am holding. If we do
> this then lets do a comprehensive job. I do not want to get through
> another cycle of this next time. At some point all this slab API stuff
> should be done.
We're gonna have API breakage with kmem_cache_ops thing too, right?
And that's not going to make it in 2.6.24 anyway, so I don't see the
problem with resending this to Andrew at -rc7 or so.
Pekka
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-07-25 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 5:48 Slab API: Remove useless ctor parameter and reorder parameters Christoph Lameter
2007-07-24 7:26 ` Christoph Lameter
2007-07-24 23:59 ` Andrew Morton
2007-07-25 0:35 ` Christoph Lameter
2007-07-25 0:53 ` Andrew Morton
2007-07-25 3:15 ` Christoph Lameter
2007-07-25 10:33 ` Pekka Enberg [this message]
2007-07-25 18:56 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2007-09-14 22:17 Christoph Lameter
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=84144f020707250333gc1c2f01l24c7b9ff6211a489@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
/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;
as well as URLs for NNTP newsgroup(s).