From: Chen Gang S <gang.chen@sunrus.com.cn>
To: sellcey@imgtec.com, Pedro Alves <palves@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org, Yao Qi <yao@codesourcery.com>
Subject: Re: [Patch] Fix build problem with system call in compile/compile.c
Date: Fri, 09 Jan 2015 03:47:00 -0000 [thread overview]
Message-ID: <54AF50E4.3080901@sunrus.com.cn> (raw)
In-Reply-To: <1420762209.2630.27.camel@ubuntu-sellcey>
On 1/9/15 08:10, Steve Ellcey wrote:
> On Thu, 2015-01-08 at 23:22 +0000, Pedro Alves wrote:
>> On 01/08/2015 10:12 PM, Steve Ellcey wrote:
>>
>>> I haven't seen any objection to
>>> Chen's patch but I haven't seen an official approval either.
>>
>> FAOD, Chen's patch is OK.
>>
>> Thanks,
>> Pedro Alves
>>
>
> Excellent. Chen Gang, do you have write access to check in this patch
> or do you need someone to do the check in for you?
>
Excuse me, I guess, I can not check in, welcome any other members help to
check in for me.
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2015-01-09 3:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 0:44 Steve Ellcey
2015-01-06 3:09 ` Yao Qi
2015-01-06 4:16 ` Joel Brobecker
2015-01-06 16:04 ` Steve Ellcey
2015-01-07 4:14 ` Joel Brobecker
2015-01-07 18:36 ` Steve Ellcey
2015-01-07 19:01 ` Pedro Alves
2015-01-07 19:29 ` Maciej W. Rozycki
2015-01-07 19:35 ` Pedro Alves
2015-01-07 23:33 ` Maciej W. Rozycki
2015-01-08 21:12 ` Jan Kratochvil
2015-01-08 22:12 ` Steve Ellcey
2015-01-08 23:22 ` Pedro Alves
2015-01-09 0:10 ` Steve Ellcey
2015-01-09 3:47 ` Chen Gang S [this message]
2015-01-09 10:11 ` Pedro Alves
2015-01-09 10:46 ` Chen Gang S
2015-01-09 20:52 ` Chen Gang S
2015-01-09 21:53 ` Chen Gang S
2015-01-10 4:30 ` Joel Brobecker
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=54AF50E4.3080901@sunrus.com.cn \
--to=gang.chen@sunrus.com.cn \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=macro@linux-mips.org \
--cc=palves@redhat.com \
--cc=sellcey@imgtec.com \
--cc=yao@codesourcery.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).