From: Greg Ungerer <gerg@linux-m68k.org>
To: torvalds@linux-foundation.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [git pull] m68knommu fixes for v4.18
Date: Tue, 3 Jul 2018 11:06:34 +1000 [thread overview]
Message-ID: <c166ef5e-89a9-1078-6a82-53c506c26f6e@linux-m68k.org> (raw)
Hi Linus,
Can you please pull the m68knommu git tree, for-linus branch.
It contains a single fix, for breakage introduced in 4.18-rc1.
Regards
Greg
The following changes since commit 021c91791a5e7e85c567452f1be3e4c2c6cb6063:
Linux 4.18-rc3 (2018-07-01 16:04:53 -0700)
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 ecd60532e060e45c63c57ecf1c8549b1d656d34d:
m68k: fix "bad page state" oops on ColdFire boot (2018-07-02 10:05:13 +1000)
----------------------------------------------------------------
Greg Ungerer (1):
m68k: fix "bad page state" oops on ColdFire boot
arch/m68k/include/asm/mcf_pgalloc.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
reply other threads:[~2018-07-03 1:06 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=c166ef5e-89a9-1078-6a82-53c506c26f6e@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).