From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>,
James Hogan <james.hogan@imgtec.com>
Cc: <linux-mips@linux-mips.org>, <markos.chandras@imgtec.com>,
Ralf Baechle <ralf@linux-mips.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MIPS64: R6: R2 emulation bugfix
Date: Thu, 30 Apr 2015 15:43:37 -0700 [thread overview]
Message-ID: <5542B019.7010303@imgtec.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1504291025430.17786@eddie.linux-mips.org>
On 04/29/2015 02:49 AM, Maciej W. Rozycki wrote:
> 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
As for me, I don't mind which solution is - STR/__stringify or __PA_ADDR.
I just would like to have one for future submissions and I assumed that
__stringify is it because it a last one so far introduced.
So, I put a decision to maintainer. Ralf?
- Leonid.
WARNING: multiple messages have this Message-ID (diff)
From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>,
James Hogan <james.hogan@imgtec.com>
Cc: linux-mips@linux-mips.org, markos.chandras@imgtec.com,
Ralf Baechle <ralf@linux-mips.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS64: R6: R2 emulation bugfix
Date: Thu, 30 Apr 2015 15:43:37 -0700 [thread overview]
Message-ID: <5542B019.7010303@imgtec.com> (raw)
Message-ID: <20150430224337.oSQe21QKYCqK0xSHq4VzS6zvtC1eWcGTxKUlB-lnQgU@z> (raw)
In-Reply-To: <alpine.LFD.2.11.1504291025430.17786@eddie.linux-mips.org>
On 04/29/2015 02:49 AM, Maciej W. Rozycki wrote:
> 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
As for me, I don't mind which solution is - STR/__stringify or __PA_ADDR.
I just would like to have one for future submissions and I assumed that
__stringify is it because it a last one so far introduced.
So, I put a decision to maintainer. Ralf?
- Leonid.
next prev parent reply other threads:[~2015-04-30 22:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 19:53 [PATCH] MIPS64: R6: R2 emulation bugfix Leonid Yegoshin
2015-04-28 19:53 ` Leonid Yegoshin
2015-04-29 9:17 ` James Hogan
2015-04-29 9:17 ` James Hogan
2015-04-29 9:49 ` Maciej W. Rozycki
2015-04-29 15:12 ` Markos Chandras
2015-04-29 15:12 ` Markos Chandras
2015-04-29 15:36 ` James Hogan
2015-04-29 15:36 ` James Hogan
2015-04-30 22:43 ` Leonid Yegoshin [this message]
2015-04-30 22:43 ` Leonid Yegoshin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5542B019.7010303@imgtec.com \
--to=leonid.yegoshin@imgtec.com \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=markos.chandras@imgtec.com \
--cc=ralf@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.