Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422725AbbD2Jt2 (ORCPT ); Wed, 29 Apr 2015 05:49:28 -0400 Received: from eddie.linux-mips.org ([148.251.95.138]:59015 "EHLO cvs.linux-mips.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422703AbbD2JtZ (ORCPT ); Wed, 29 Apr 2015 05:49:25 -0400 Date: Wed, 29 Apr 2015 10:49:21 +0100 (BST) From: "Maciej W. Rozycki" To: James Hogan cc: Leonid Yegoshin , linux-mips@linux-mips.org, markos.chandras@imgtec.com, Ralf Baechle , linux-kernel@vger.kernel.org Subject: Re: [PATCH] MIPS64: R6: R2 emulation bugfix In-Reply-To: <5540A1BF.7060408@imgtec.com> Message-ID: References: <20150428195335.11229.4516.stgit@ubuntu-yegoshin> <5540A1BF.7060408@imgtec.com> User-Agent: Alpine 2.11 (LFD 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1183 Lines: 31 On Wed, 29 Apr 2015, James Hogan wrote: > > Error recovery pointers for fixups was improperly set as ".word" > > which is unsuitable for MIPS64. > > > > Replaced by __stringify(PTR) > > Every other case of this sort of thing uses STR(PTR) (or __UA_ADDR in > uaccess.h). Can we stick to STR(PTR) for consistency please? Or __PA_ADDR in paccess.h. I have mixed feelings, the reason for __stringify being absent is the macro being generic and more recently added than pieces of code that use STR, e.g. unaligned.c that has been there since forever. And we do use __stringify in many other cases. On the other hand STR is short and sweet, unlike __stringify. So how about adding a macro like __STR_PTR that expands to __stringify(PTR) and converting all the places throughout our port (including ones currently using __UA_ADDR/__PA_ADDR) to use the new macro? Leonid's bug fix will need to go in first of course. Maciej -- 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/