From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org
Cc: dhowells@redhat.com, takeuchi.akr@jp.panasonic.com,
linux-am33-list@redhat.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] MN10300 Fixes
Date: Sat, 29 Jun 2013 00:01:48 +0100 [thread overview]
Message-ID: <20468.1372460508@warthog.procyon.org.uk> (raw)
Hi Linus,
Could you pull these MN10300 fixes please? The first fixes a problem with
passing arrays rather than pointers to get_user() where __typeof__ then wants
to declare and initialise an array variable which gcc doesn't like. The
second fixes a problem whereby putting mem=xxx into the kernel command line
causes init=xxx to get an incorrect value.
Thanks,
David
---
The following changes since commit 98b6ed0f2bf4abfb759206aa70690636372bdee7:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2013-06-26 19:24:37 -1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-mn10300.git tags/for-linus-20130628
for you to fetch changes up to e3f12a53042e26202993baa3ad4ff8768173653d:
mn10300: Use early_param() to parse "mem=" parameter (2013-06-28 16:53:03 +0100)
----------------------------------------------------------------
(from the branch description for for-linus local branch)
MN10300 patches for linus
MN10300 changes 2013-06-28
----------------------------------------------------------------
Akira Takeuchi (2):
mn10300: Allow to pass array name to get_user()
mn10300: Use early_param() to parse "mem=" parameter
arch/mn10300/include/asm/uaccess.h | 2 +-
arch/mn10300/kernel/setup.c | 54 +++++++++++++++-----------------------
2 files changed, 22 insertions(+), 34 deletions(-)
reply other threads:[~2013-06-28 23:01 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=20468.1372460508@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-am33-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=takeuchi.akr@jp.panasonic.com \
--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
all inboxes | Powered by JetHome®