From: Angelo Dureghello <angelo@sysam.it>
To: Greg Ungerer <gerg@linux-m68k.org>, linux-m68k@vger.kernel.org
Cc: geert@linux-m68k.org
Subject: Re: [PATCH 0/3] m68k: coldfire MMU fixes
Date: Sat, 9 Sep 2017 00:33:51 +0200 [thread overview]
Message-ID: <c2d0637b-0e6c-dfff-88d1-1de7990b0294@sysam.it> (raw)
In-Reply-To: <1504854061-12830-1-git-send-email-gerg@linux-m68k.org>
Dear Greg,
On 08/09/2017 09:00, Greg Ungerer wrote:
> The following patch series fixes some issues with the initialization phase
> of the ColdFire MMU system startup. With these fixes applied we can also
> enable and run the ColdFire 5441x family of parts with their MMU enabled.
>
> arch/m68k/Kconfig.cpu | 2 +-
> arch/m68k/coldfire/m54xx.c | 4 ----
> arch/m68k/include/asm/mcfmmu.h | 1 +
> arch/m68k/include/asm/mmu_context.h | 1 -
> arch/m68k/kernel/setup_mm.c | 2 ++
> arch/m68k/mm/mcfmmu.c | 4 ++--
> 6 files changed, 6 insertions(+), 8 deletions(-)
>
I just applied this patchset to fresh master and re-verified that enabling
MMU works on my mcf54415 based board.
Tested-by: Angelo Dureghello <angelo@sysam.it>
Regards,
Angelo Dureghello
> --
> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2017-09-08 22:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 7:00 [PATCH 0/3] m68k: coldfire MMU fixes Greg Ungerer
2017-09-08 7:00 ` [PATCH 1/3] m68k: move coldfire MMU initialization code Greg Ungerer
2017-09-08 7:01 ` [PATCH 2/3] m68k: fix ColdFire node shift size calculation Greg Ungerer
2017-09-08 7:01 ` [PATCH 3/3] m68k: allow ColdFire m5441x parts to run with MMU enabled Greg Ungerer
2017-09-08 22:33 ` Angelo Dureghello [this message]
2017-09-11 3:08 ` [PATCH 0/3] m68k: coldfire MMU fixes Greg Ungerer
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=c2d0637b-0e6c-dfff-88d1-1de7990b0294@sysam.it \
--to=angelo@sysam.it \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-m68k@vger.kernel.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