From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH v2] m68k: merge the mmu and non-mmu versions of ptrace.c
Date: Wed, 22 Feb 2012 21:37:47 +1000 [thread overview]
Message-ID: <4F44D38B.6060303@snapgear.com> (raw)
In-Reply-To: <CAMuHMdVD-QuZ+HEEuJFXp2=H=XZum+QVqw36LWKu_6jboCMKMA@mail.gmail.com>
Hi Geert,
On 02/22/2012 07:41 PM, Geert Uytterhoeven wrote:
> On Wed, Feb 22, 2012 at 04:13,<gerg@snapgear.com> wrote:
>> Most of the code in the non-mmu ptrace_no.c file is the same as the mmu
>> version ptrace_mm.c. So merge them back into a single file.
>>
>> Signed-off-by: Greg Ungerer<gerg@uclinux.org>
>
> Acked-by: Geert Uytterhoeven<geert@linux-m68k.org>
Thanks!
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close, FAX: +61 7 3891 3630
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
prev parent reply other threads:[~2012-02-22 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 3:13 [PATCH v2] m68k: merge the mmu and non-mmu versions of ptrace.c gerg
2012-02-22 9:41 ` Geert Uytterhoeven
2012-02-22 11:37 ` Greg Ungerer [this message]
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=4F44D38B.6060303@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.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