From: Paul Mundt <lethal@linux-sh.org>
To: roel kluin <roel.kluin@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: correct definitions to access stack pointers
Date: Wed, 05 Jan 2011 07:57:38 +0000 [thread overview]
Message-ID: <20110105075737.GB23889@linux-sh.org> (raw)
In-Reply-To: <4D1F7434.4090108@gmail.com>
On Sat, Jan 01, 2011 at 07:36:36PM +0100, roel kluin wrote:
> A definition like:
>
> #define regs_return_value(regs) ((regs)->regs[0])
>
> called with regs_return_value(foo) will be preprocessed to:
>
> ((foo)->foo[0])
> ^^^
> So to fix this to ensure the preprocessor compiles such calls correctly.
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: roel kluin <roel.kluin@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: correct definitions to access stack pointers
Date: Wed, 5 Jan 2011 16:57:38 +0900 [thread overview]
Message-ID: <20110105075737.GB23889@linux-sh.org> (raw)
In-Reply-To: <4D1F7434.4090108@gmail.com>
On Sat, Jan 01, 2011 at 07:36:36PM +0100, roel kluin wrote:
> A definition like:
>
> #define regs_return_value(regs) ((regs)->regs[0])
>
> called with regs_return_value(foo) will be preprocessed to:
>
> ((foo)->foo[0])
> ^^^
> So to fix this to ensure the preprocessor compiles such calls correctly.
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
Applied, thanks.
next prev parent reply other threads:[~2011-01-05 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 18:36 [PATCH] sh: correct definitions to access stack pointers roel kluin
2011-01-01 18:36 ` roel kluin
2011-01-05 7:57 ` Paul Mundt [this message]
2011-01-05 7:57 ` Paul Mundt
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=20110105075737.GB23889@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=roel.kluin@gmail.com \
/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.