mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Pekka Enberg <penberg@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] SLAB changes for v3.9-rc1
Date: Wed, 6 Mar 2013 16:38:33 +0000	[thread overview]
Message-ID: <0000013d40918dba-4b124e7a-e591-4e75-b568-e1ff9a8d9f03-000000@email.amazonses.com> (raw)
In-Reply-To: <CA+55aFxV=xs9a8H1YbFSjNzMeebixFaA4hShdHwfRKndFU8FUA@mail.gmail.com>

On Tue, 5 Mar 2013, Linus Torvalds wrote:

> On Mon, Mar 4, 2013 at 2:35 AM, Pekka Enberg <penberg@kernel.org> wrote:
> >
> > It contains more of Christoph's SLAB unification work that reduce the
> > differences between different slab allocators. The code has been sitting
> > in linux-next without problems.
> >
> > If you feel this is inappropriate for -rc2, just skip the pull and I'll
> > requeue it for 3.10.
>
> Ugh. It only came a day late, and if you had pushed a bit harder, I'd
> have pulled it. But when you put it that way, I really cannot see any
> valid reason why it cannot wait, and so I think I'll just expect it
> for the next release.
>
> If you change your mind and realize that it fixes some major bug and
> really needs to be pulled after all, holler.

Well this stuff was already ready for 3.8 and missed that merge period as
well. There are a couple of bug fixes included as well. It is the basis
for more common code between allocators. Most of it is renaming things so
that fields have a common name which enables more code sharing.



  reply	other threads:[~2013-03-06 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04 10:35 Pekka Enberg
2013-03-06  2:32 ` Linus Torvalds
2013-03-06 16:38   ` Christoph Lameter [this message]
2013-03-06 20:40     ` Pekka Enberg

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=0000013d40918dba-4b124e7a-e591-4e75-b568-e1ff9a8d9f03-000000@email.amazonses.com \
    --to=cl@linux.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®