From: Yao Qi <yao@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: Ping: Merge duplicated macros in linux-nat.c and linux-low.c
Date: Fri, 11 Mar 2011 05:05:00 -0000 [thread overview]
Message-ID: <4D79A0F3.8060908@codesourcery.com> (raw)
In-Reply-To: <4D6B96DC.5090606@codesourcery.com>
On 02/28/2011 08:36 PM, Yao Qi wrote:
> On 02/20/2011 11:05 PM, Yao Qi wrote:
>> All the comments in previous mails are address in this new patch,
>> 1. rename 'linux-common.h' to 'linux-ptrace.h', which includes only
>> ptrace-related macros.
>> 2. include <sys/wait.h> in linux-ptrace.h for macro __WALL,
>> 3. add dependency tracking for gdbserver,
>
>> gdb/
>>
>> * linux-nat.c: Move common macros to ...
>> Include linux-ptrace.h.
>> * common/linux-ptrace.h: ... here. New.
>>
>> gdb/gdbserver/
>>
>> * linux-low.c: Move common macros to linux-ptrace.h.
>> Include linux-ptrace.h.
>> * Makefile.in (linux_ptrace_h): New.
>> (linux-low.o): Depends on linux-ptrace.h.
>>
>
> Ping.
>
Ping?
Since configure/make issues in common/ has been resolved, can I apply
this patch to mainline? Or apply it after 7.3 branch is created?
--
Yao (é½å°§)
next prev parent reply other threads:[~2011-03-11 4:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 8:24 [common] " Yao Qi
2011-02-18 9:36 ` Jan Kratochvil
2011-02-18 14:54 ` Yao Qi
2011-02-18 15:14 ` Mark Kettenis
2011-02-18 16:14 ` Pedro Alves
2011-02-18 15:24 ` Tom Tromey
2011-02-18 15:46 ` Yao Qi
2011-02-18 15:55 ` Tom Tromey
2011-02-18 15:52 ` Pedro Alves
2011-02-18 17:21 ` Yao Qi
2011-02-20 21:34 ` Yao Qi
2011-02-28 12:38 ` Ping: " Yao Qi
2011-02-28 14:35 ` question about the common/ subdir (was "Re: Ping: Merge duplicated macros in linux-nat.c and linux-low.c") Joel Brobecker
2011-02-28 14:54 ` Yao Qi
2011-02-28 15:11 ` Pedro Alves
2011-02-28 15:00 ` Pedro Alves
2011-03-11 5:05 ` Yao Qi [this message]
2011-03-29 7:46 ` Ping: Merge duplicated macros in linux-nat.c and linux-low.c Yao Qi
2011-04-07 14:06 ` Yao Qi
2011-04-25 17:04 ` [common] " Tom Tromey
2011-04-26 15:39 ` Yao Qi
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=4D79A0F3.8060908@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox