From: Borislav Petkov <bp@alien8.de>
To: x86-ml <x86@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/mm updates
Date: Thu, 19 Feb 2015 09:50:59 +0100 [thread overview]
Message-ID: <20150219085059.GC31218@pd.tnic> (raw)
Hi guys,
please pull, thanks.
---
The following changes since commit bfa76d49576599a4b9f9b7a71f23d73d6dcff735:
Linux 3.19 (2015-02-08 18:54:22 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/tip_x86_mm
for you to fetch changes up to aaaf74be58dc020ca355f5e19adda0038a54b2dd:
x86: Fix wrong page size in init_memory_mapping() printks (2015-02-12 19:45:38 +0100)
----------------------------------------------------------------
* Fix page size printing during early boot on 32-bit, by Dave Hansen.
----------------------------------------------------------------
Dave Hansen (1):
x86: Fix wrong page size in init_memory_mapping() printks
arch/x86/mm/init.c | 28 ++++++++++++++++++++++++++--
1 file changed, 26 insertions(+), 2 deletions(-)
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
reply other threads:[~2015-02-19 8:51 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=20150219085059.GC31218@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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