From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Sat, 04 Apr 2015 22:05:01 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1]:60804 "EHLO linux-mips.org" rhost-flags-OK-OK-OK-FAIL) by eddie.linux-mips.org with ESMTP id S27010451AbbDDUE7dBQ87 (ORCPT ); Sat, 4 Apr 2015 22:04:59 +0200 Received: from scotty.linux-mips.net (localhost.localdomain [127.0.0.1]) by scotty.linux-mips.net (8.14.9/8.14.8) with ESMTP id t34K50ph010040; Sat, 4 Apr 2015 22:05:00 +0200 Received: (from ralf@localhost) by scotty.linux-mips.net (8.14.9/8.14.9/Submit) id t34K4xRn010039; Sat, 4 Apr 2015 22:04:59 +0200 Date: Sat, 4 Apr 2015 22:04:59 +0200 From: Ralf Baechle To: "Maciej W. Rozycki" Cc: linux-mips@linux-mips.org Subject: Re: [PATCH 00/48] FPU and FP emulation clean-ups, fixes and feature updates Message-ID: <20150404200459.GE20157@linux-mips.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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: 46779 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: ralf@linux-mips.org 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 Fri, Apr 03, 2015 at 11:23:29PM +0100, Maciej W. Rozycki wrote: > These are fixes to address code structuring and coding style problems > and then bug fixes I discovered in the course of implementing an > upcoming FPU feature. There are some minor feature updates too. They > are related to one another to a various extent, sometimes very loosely, > but I decided to keep them as a series because there is a lot of > syntactical overlap, as changes are made in steps, one issue at a time. > Keeping them in order guarantees that they apply on top of one another. > > Clean-ups come first as they should be completely uncontroversial, > followed by restructuring, bug fixes and new features. It would have been nice if the bug fixes or at least those relevant to 4.0 and older were at the beginning to reduce issue when applying them to the 4.0-fixes and possibly -stable branches. I applied your patches on top of my working branch and ran into a number of conflicts. Will push the result out as soon as I'm done with the conflict resolution. Thanks! Ralf