Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932277AbWAJRNz (ORCPT ); Tue, 10 Jan 2006 12:13:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932286AbWAJRNz (ORCPT ); Tue, 10 Jan 2006 12:13:55 -0500 Received: from mx.pathscale.com ([64.160.42.68]:34203 "EHLO mx.pathscale.com") by vger.kernel.org with ESMTP id S932277AbWAJRNy (ORCPT ); Tue, 10 Jan 2006 12:13:54 -0500 Subject: Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32 From: "Bryan O'Sullivan" To: Christoph Hellwig Cc: Roland Dreier , sam@ravnborg.org, Andrew Morton , linux-kernel@vger.kernel.org In-Reply-To: <20060110170722.GA3187@infradead.org> References: <20060110011844.7a4a1f90.akpm@osdl.org> <1136909276.32183.28.camel@serpentine.pathscale.com> <20060110170722.GA3187@infradead.org> Content-Type: text/plain Organization: PathScale, Inc. Date: Tue, 10 Jan 2006 09:13:51 -0800 Message-Id: <1136913231.6294.2.camel@serpentine.pathscale.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 874 Lines: 24 On Tue, 2006-01-10 at 17:07 +0000, Christoph Hellwig wrote: > Or add a CONFIG_GENERIC_MEMCPY_IO that's non-uservisible and just set > by all the architectures that don't provide their own version. That's only very slightly different from the RFC patch I just posted. If you think it would be a preferable way to express it, that's fine by me. It would at least keep me from crapping on every arch's lib/Makefile. > And once > we're at that level of complexity we should really add the _fromio version > aswell I'm already being raked over the coals enough for a routine that has an actual user waiting in the wings :-)