From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Tue, 18 Aug 2015 07:38:27 +0200 (CEST) Received: from verein.lst.de ([213.95.11.211]:55009 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S27006157AbbHRFiZwvJxg (ORCPT ); Tue, 18 Aug 2015 07:38:25 +0200 Received: by newverein.lst.de (Postfix, from userid 2407) id 6C6C0691E9; Tue, 18 Aug 2015 07:38:25 +0200 (CEST) Date: Tue, 18 Aug 2015 07:38:25 +0200 From: Christoph Hellwig To: Andrew Morton Cc: arnd@arndb.de, linux@arm.linux.org.uk, catalin.marinas@arm.com, will.deacon@arm.com, ysato@users.sourceforge.jp, monstr@monstr.eu, jonas@southpole.se, cmetcalf@ezchip.com, gxt@mprc.pku.edu.cn, x86@kernel.org, linux-alpha@vger.kernel.org, linux-hexagon@vger.kernel.org, linux-ia64@vger.kernel.org, linux-mips@linux-mips.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: provide more common DMA API functions V2 Message-ID: <20150818053825.GA20771@lst.de> References: <1439795216-32189-1-git-send-email-hch@lst.de> <20150817142429.95a3965e0b35d0f35d3c4cfe@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150817142429.95a3965e0b35d0f35d3c4cfe@linux-foundation.org> User-Agent: Mutt/1.5.17 (2007-11-01) Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 48927 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: hch@lst.de Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips On Mon, Aug 17, 2015 at 02:24:29PM -0700, Andrew Morton wrote: > 110254 bytes saved, shrinking the kernel by a whopping 0.17%. > Thoughts? Sounds fine to me. > > I'll merge these 5 patches for 4.3. That means I'll release them into > linux-next after 4.2 is released. So you only add for-4.3 code to -next after 4.2 is odd? Isn't thast the wrong way around?