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] m68k: merge the init_task code for mmu and non-mmu targets
Date: Sun, 11 Dec 2011 21:26:08 +1000 [thread overview]
Message-ID: <4EE49350.1040902@snapgear.com> (raw)
In-Reply-To: <CAMuHMdWE7NLs9zeMRZ_iAcY2P8Zjd8OYUeY5bfHyK-6=hzbVbA@mail.gmail.com>
On 12/11/2011 07:21 PM, Geert Uytterhoeven wrote:
> On Fri, Sep 2, 2011 at 07:20,<gerg@snapgear.com> wrote:
>> From: Greg Ungerer<gerg@uclinux.org>
>>
>> The init_task code can be the same for both mmu and non-mmu targets.
>> None of the alignment carried out in the the current init_task code
>> is necessary. The linker script takes care of aligning the init_thread
>> structure to a THREAD SIZE boundary, and that is all we need.
>>
>> So use the init_task.c code for all target types, that makes m68k
>> code consistent with what most other architectures do.
>>
>> Signed-off-by: Greg Ungerer<gerg@uclinux.org>
>
> Acked-by: Geert Uytterhoeven<geert@linux-m68k.org>
Thanks Geert!
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:[~2011-12-11 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 5:20 [PATCH] m68k: merge the init_task code for mmu and non-mmu targets gerg
2011-12-11 9:21 ` Geert Uytterhoeven
2011-12-11 11:26 ` 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=4EE49350.1040902@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.