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 4/5 v2] m68k: merge mmu and non-mmu versions of time.c
Date: Wed, 22 Feb 2012 21:41:05 +1000 [thread overview]
Message-ID: <4F44D451.90209@snapgear.com> (raw)
In-Reply-To: <CAMuHMdWwz8ou5fDKOb7Ef8fgn8aHCEzXigp1CBWqPc9w6+FUeg@mail.gmail.com>
Hi Geert,
On 02/22/2012 07:42 PM, Geert Uytterhoeven wrote:
> On Wed, Feb 22, 2012 at 04:58,<gerg@snapgear.com> wrote:
>> There is only trivial differences between the mmu time_mm.c and non-mmu
>> time_no.c files. Merge them back into a single time.c.
>>
>> Signed-off-by: Greg Ungerer<gerg@uclinux.org>
>
> Acked-by: Geert Uytterhoeven<geert@linux-m68k.org>
Thanks for these acks too!
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
next prev parent reply other threads:[~2012-02-22 11:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 3:58 [PATCH 1/5 v2] m68knommu: make persistent clock code consistent with m68k gerg
2012-02-22 3:58 ` [PATCH 2/5 v2] m68knommu: modify timer init code to make it consistent with m68k code gerg
2012-02-22 3:58 ` [PATCH 3/5 v2] m68knommu: remove unused CONFIG_GENERIC_CMOS_UPDATE option gerg
2012-02-22 3:58 ` [PATCH 4/5 v2] m68k: merge mmu and non-mmu versions of time.c gerg
2012-02-22 9:42 ` Geert Uytterhoeven
2012-02-22 11:41 ` Greg Ungerer [this message]
2012-02-22 3:58 ` [PATCH 5/5 v2] m68k: remove dead timer code gerg
2012-02-22 10:05 ` Geert Uytterhoeven
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=4F44D451.90209@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 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.