Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753941AbYJTSEQ (ORCPT ); Mon, 20 Oct 2008 14:04:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752298AbYJTSEA (ORCPT ); Mon, 20 Oct 2008 14:04:00 -0400 Received: from waste.org ([66.93.16.53]:37262 "EHLO waste.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752084AbYJTSEA (ORCPT ); Mon, 20 Oct 2008 14:04:00 -0400 Subject: Re: [PATCH] Export tiny shmem_file_setup for DRM-GEM From: Matt Mackall To: Hugh Dickins Cc: Dave Airlie , Keith Packard , Eric Anholt , Nick Piggin , David Howells , linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Date: Mon, 20 Oct 2008 13:02:34 -0500 Message-Id: <1224525754.4323.21.camel@calx> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 931 Lines: 22 On Sun, 2008-10-19 at 12:52 +0100, Hugh Dickins wrote: > We're trying to keep the !CONFIG_SHMEM tiny-shmem.c (using ramfs without > swap) in synch with CONFIG_SHMEM shmem.c (and mpm is preparing patches > to combine them). I was glad to see EXPORT_SYMBOL_GPL(shmem_file_setup) > go into shmem.c, but why not support DRM-GEM when !CONFIG_SHMEM too? > But caution says still depend on MMU, since !CONFIG_MMU is.. different. > > Signed-off-by: Hugh Dickins Acked-by: Matt Mackall Hugh, what path do you usually take for upstreaming shmem bits and what path should I take with my unify patch? -- Mathematics is the supreme nostalgia of our time. -- 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/