From: Hui Zhu <teawater@gmail.com>
To: oza Pawandeep <oza.pawandeep@gmail.com>
Cc: Yao Qi <yao@codesourcery.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Makefile.in includes linux-record.c to be common for all arch. (arm-reversible>phase-3)
Date: Mon, 18 Jun 2012 14:22:00 -0000 [thread overview]
Message-ID: <CANFwon1JqxWMosYH8nWHDfD+k38P2sZv7xphJoGe94qUdu7HZg@mail.gmail.com> (raw)
In-Reply-To: <CAK1A=4yoRwSsWXLGy9den5vYNBoEvpBsH4T-=OQiAsqt4zaTrA@mail.gmail.com>
On Mon, Jun 18, 2012 at 7:49 PM, oza Pawandeep <oza.pawandeep@gmail.com> wrote:
> Yes I agree; as I integrated both of them and post them at once.
> sorry about confusion; this patch has to be ignored.
>
> In fact I wanted this patch to be approved first because without which
> sys call patch would not compile.
Why you cannot commit a patch list when the function is done?
I think the function in the trunk tree need be done before commit to
it. If you want work in cvs, I suggest you use the branch first.
On the other hand, I heard that some of code of arm record is checked
in. I don't think it is right. Because without syscall support, it
cannot work, right?
So what I suggest is move all the code about arm record to a separate
branch. And when all of the arm record function done, you re-send all
of them.
Thanks,
Hui
>
> Regards,
> Oza.
>
> On Mon, Jun 18, 2012 at 2:54 PM, Yao Qi <yao@codesourcery.com> wrote:
>> On 06/18/2012 05:08 PM, oza Pawandeep wrote:
>>> diff -urN orig/configure.tgt new/configure.tgt
>>> --- orig/configure.tgt 2012-06-18 12:36:47.274501400 +0530
>>> +++ new/configure.tgt 2012-06-18 12:31:47.335501400 +0530
>>> @@ -76,7 +76,7 @@
>>> arm*-*-linux*)
>>> # Target: ARM based machine running GNU/Linux
>>> gdb_target_obs="arm-tdep.o arm-linux-tdep.o glibc-tdep.o \
>>> - solib-svr4.o symfile-mem.o linux-tdep.o"
>>> + solib-svr4.o symfile-mem.o linux-tdep.o linux-record.o"
>>> build_gdbserver=yes
>>> ;;
>>> arm*-*-netbsd* | arm*-*-knetbsd*-gnu)
>>>
>>> ok to check in ?
>>
>> It is not good to post the same change twice in different mails. This
>> change makes no sense until your 'arm-syscall record' patch is approved.
>> I noticed that this change has been included in your 'arm-syscall
>> record' patch, so I think patch here doesn't have to reviewed.
>>
>> --
>> Yao (齐尧)
>>
>>
next prev parent reply other threads:[~2012-06-18 14:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 3:51 oza Pawandeep
2012-06-07 13:41 ` Yao Qi
2012-06-07 17:20 ` oza Pawandeep
2012-06-08 6:09 ` Matt Rice
2012-06-08 12:45 ` oza Pawandeep
2012-06-18 9:08 ` oza Pawandeep
2012-06-18 9:24 ` Yao Qi
2012-06-18 11:49 ` oza Pawandeep
2012-06-18 14:22 ` Hui Zhu [this message]
[not found] ` <CAK1A=4wdqiGCGGQuQHmDB19O=RfjttaG9M83KpBkuUyQPd=0qQ@mail.gmail.com>
2012-06-18 18:55 ` oza Pawandeep
2012-06-19 1:35 ` Hui Zhu
2012-06-19 5:13 ` oza Pawandeep
2012-06-19 16:03 ` oza Pawandeep
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=CANFwon1JqxWMosYH8nWHDfD+k38P2sZv7xphJoGe94qUdu7HZg@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=oza.pawandeep@gmail.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