From: Greg Ungerer <gerg@uclinux.org>
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.9
Date: Mon, 11 Mar 2013 10:32:26 +1000 [thread overview]
Message-ID: <201303110032.r2B0WQXC024689@goober.accelcon.com> (raw)
Hi Linus,
Can you please pull the m68knommu git tree, for-linus branch.
It contains a few small fixes for the non-MMU m68k platforms. Fixes some
compilation problems, some broken header definitions, removes an unused
config option and adds a name for the old 68000 CPU support.
Regards
Greg
The following changes since commit 6dbe51c251a327e012439c4772097a13df43c5b8:
Linux 3.9-rc1 (2013-03-03 15:11:05 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git for-linus
for you to fetch changes up to ef9240f482e691e13a2d27208f60d1f1f5503545:
m68k: drop "select EMAC_INC" (2013-03-06 16:08:26 +1000)
----------------------------------------------------------------
Greg Ungerer (1):
m68knommu: fix misnamed GPIO pin definition for ColdFire 528x CPU
Luis Alves (2):
m68knommu: add CPU_NAME for 68000
m68knommu: fix MC68328.h defines
Paul Bolle (1):
m68k: drop "select EMAC_INC"
Thadeu Lima de Souza Cascardo (1):
m68knommu: fix build when CPU is not coldfire
arch/m68k/Kconfig.machine | 1 -
arch/m68k/include/asm/MC68328.h | 10 +++++-----
arch/m68k/kernel/setup_no.c | 3 +++
arch/m68k/mm/init.c | 2 +-
arch/m68k/platform/coldfire/m528x.c | 2 +-
5 files changed, 10 insertions(+), 8 deletions(-)
next reply other threads:[~2013-03-11 0:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 0:32 Greg Ungerer [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-04-13 7:45 [git pull] m68knommu arch fixes for 3.9 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=201303110032.r2B0WQXC024689@goober.accelcon.com \
--to=gerg@uclinux.org \
--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