From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Roel Kluin <roel.kluin@gmail.com>
Cc: Jeff Dike <jdike@addtoit.com>,
lkml <linux-kernel@vger.kernel.org>,
uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] [PATCH] x86, um: fix EXECUTE_SYSCALL macros
Date: Fri, 23 Jan 2009 00:05:25 +0800 [thread overview]
Message-ID: <20090122160525.GB9732@hack.private> (raw)
In-Reply-To: <497890C2.1040206@gmail.com>
On Thu, Jan 22, 2009 at 04:29:06PM +0100, Roel Kluin wrote:
>Roel Kluin wrote:
>> When these macros aren't called with regs, e.g. with foo
>> this will incorectly expand to foo->foo.gp[*]
>>
>> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
>> ---
>> My other patch should probably as well have been sent to this list:
>> http://lkml.org/lkml/2009/1/21/203
>>
>there were more
>
>Fix EXECUTE_SYSCALL macros. When called with a variable named other
>than regs as second argument, this will result in a build failure.
>
>Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
Reviewed-by: WANG Cong <wangcong@zeuux.org>
--
"Against stupidity, the gods themselves, contend in vain."
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Roel Kluin <roel.kluin@gmail.com>
Cc: Jeff Dike <jdike@addtoit.com>,
lkml <linux-kernel@vger.kernel.org>,
uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [PATCH] x86, um: fix EXECUTE_SYSCALL macros
Date: Fri, 23 Jan 2009 00:05:25 +0800 [thread overview]
Message-ID: <20090122160525.GB9732@hack.private> (raw)
In-Reply-To: <497890C2.1040206@gmail.com>
On Thu, Jan 22, 2009 at 04:29:06PM +0100, Roel Kluin wrote:
>Roel Kluin wrote:
>> When these macros aren't called with regs, e.g. with foo
>> this will incorectly expand to foo->foo.gp[*]
>>
>> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
>> ---
>> My other patch should probably as well have been sent to this list:
>> http://lkml.org/lkml/2009/1/21/203
>>
>there were more
>
>Fix EXECUTE_SYSCALL macros. When called with a variable named other
>than regs as second argument, this will result in a build failure.
>
>Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
Reviewed-by: WANG Cong <wangcong@zeuux.org>
--
"Against stupidity, the gods themselves, contend in vain."
next prev parent reply other threads:[~2009-01-22 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 15:15 [uml-devel] [PATCH] x86, um: fix GETREG/PUTREG macros Roel Kluin
2009-01-21 15:15 ` Roel Kluin
2009-01-22 15:29 ` [uml-devel] [PATCH] x86, um: fix EXECUTE_SYSCALL macros Roel Kluin
2009-01-22 15:29 ` Roel Kluin
2009-01-22 16:05 ` Américo Wang [this message]
2009-01-22 16:05 ` Américo Wang
2009-01-22 16:04 ` [uml-devel] [PATCH] x86, um: fix GETREG/PUTREG macros Américo Wang
2009-01-22 16:04 ` Américo Wang
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=20090122160525.GB9732@hack.private \
--to=xiyou.wangcong@gmail.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roel.kluin@gmail.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.