From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Mon, 07 Aug 2017 12:09:41 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1]:46038 "EHLO linux-mips.org" rhost-flags-OK-OK-OK-FAIL) by eddie.linux-mips.org with ESMTP id S23991087AbdHGKJdMdmEn (ORCPT ); Mon, 7 Aug 2017 12:09:33 +0200 Received: from h7.dl5rb.org.uk (localhost [127.0.0.1]) by h7.dl5rb.org.uk (8.15.2/8.14.8) with ESMTP id v77A9Vwl025794; Mon, 7 Aug 2017 12:09:31 +0200 Received: (from ralf@localhost) by h7.dl5rb.org.uk (8.15.2/8.15.2/Submit) id v77A9VbD025793; Mon, 7 Aug 2017 12:09:31 +0200 Date: Mon, 7 Aug 2017 12:09:31 +0200 From: Ralf Baechle To: Aleksandar Markovic Cc: linux-mips@linux-mips.org, Aleksandar Markovic , Miodrag Dinic , Goran Ferenc , "# 4 . 3+" , Bo Hu , Douglas Leung , James Hogan , Jin Qian , linux-kernel@vger.kernel.org, Paul Burton , Petar Jovanovic , Raghu Gandham Subject: Re: [PATCH v4 05/16] MIPS: math-emu: .: Fix quiet NaN propagation Message-ID: <20170807100931.GA25642@linux-mips.org> References: <1501171791-23690-1-git-send-email-aleksandar.markovic@rt-rk.com> <1501171791-23690-6-git-send-email-aleksandar.markovic@rt-rk.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1501171791-23690-6-git-send-email-aleksandar.markovic@rt-rk.com> User-Agent: Mutt/1.8.3 (2017-05-23) 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: 59389 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 Thu, Jul 27, 2017 at 06:08:48PM +0200, Aleksandar Markovic wrote: This is a mindbogglingly big series of FP fixes. There's always a risk associated with fixes so I'd prefer if they could wait for 4.14. For now I'm going to apply them to my 4.14 branch but let me know if you think they are more urgent than that? Ralf