Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755245Ab3CFUkz (ORCPT ); Wed, 6 Mar 2013 15:40:55 -0500 Received: from mail-wi0-f182.google.com ([209.85.212.182]:49016 "EHLO mail-wi0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754999Ab3CFUkx (ORCPT ); Wed, 6 Mar 2013 15:40:53 -0500 MIME-Version: 1.0 In-Reply-To: <0000013d40918dba-4b124e7a-e591-4e75-b568-e1ff9a8d9f03-000000@email.amazonses.com> References: <0000013d40918dba-4b124e7a-e591-4e75-b568-e1ff9a8d9f03-000000@email.amazonses.com> Date: Wed, 6 Mar 2013 22:40:52 +0200 X-Google-Sender-Auth: vgz4p69Lgo0_3e1lOtG87GTcN4U Message-ID: Subject: Re: [GIT PULL] SLAB changes for v3.9-rc1 From: Pekka Enberg To: Christoph Lameter Cc: Linus Torvalds , Andrew Morton , Linux Kernel Mailing List Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1100 Lines: 23 Hi Christoph, On Wed, Mar 6, 2013 at 6:38 PM, Christoph Lameter wrote: > 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. It was me who missed the merge window - sorry about that. But is there really any real need to push this through at such late stage? People will work on "slab/next" branch anyway so what's the rush? We had quite a lot of changes due to slab memcg and I'd rather keep things calm for this release cycle. It usually takes a few cycles for people to start noticing problems and it doesn't really help if there's code churn going on all the time. Pekka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/