From: Greg Ungerer <gerg@goober.accelcon.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
uclinux-dev@uclinux.org, geert@linux-m68k.org
Subject: [git pull] m68knommu arch fixes for 3.8
Date: Fri, 18 Jan 2013 16:47:16 +1000 [thread overview]
Message-ID: <201301180647.r0I6lGbf020653@goober.accelcon.com> (raw)
Hi Linus,
Can you please pull the m68knommu git tree, for-linus branch, at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git for-linus
It contains a couple of fixes, both affecting compilation of non-mmu m68k
targets.
Regards
Greg
The following changes since commit d1c3ed669a2d452cacfb48c2d171a1f364dae2ed:
Linus Torvalds (1):
Linux 3.8-rc2
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git for-linus
Greg Ungerer (2):
m68knommu: add KMAP definitions for non-MMU definitions
m68k: fix conditional use of init_pointer_table
arch/m68k/include/asm/pgtable_no.h | 2 ++
arch/m68k/mm/init.c | 8 +++++---
2 files changed, 7 insertions(+), 3 deletions(-)
reply other threads:[~2013-01-18 8:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201301180647.r0I6lGbf020653@goober.accelcon.com \
--to=gerg@goober.accelcon.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@linux-foundation.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