From: Jonas Bonn <jonas@southpole.se>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Build fixes for OpenRISC arch
Date: Wed, 29 Feb 2012 10:30:00 +0100 [thread overview]
Message-ID: <1330507800.2964.52.camel@crucifix> (raw)
Hi Linus,
I know my GPG key isn't in your web of trust, but I figured I'd do a
signed pull request anyway. The server to pull from is the usual one so
things are about the same as if I'd just asked you to pull a branch.
There's just two small fixes here to enable building the OpenRISC
architecture after changes elsewhere in the kernel didn't get propagated
all the way through into this arch. Both pretty trivial.
/Jonas
The following changes since commit
d65b4e98d7ea3038b767b70fe8be959b2913f16d:
Linux 3.3-rc3 (2012-02-08 19:21:53 -0800)
are available in the git repository at:
git://openrisc.net/jonas/linux for-3.3
for you to fetch changes up to 3f6ffc8c2087791920721f086f9a92fde7bed9e2:
openrisc: Fix up audit_syscall_[entry|exit]() usage (2012-02-17
09:53:12 +0100)
----------------------------------------------------------------
Build fixes for 3.3
----------------------------------------------------------------
Jonas Bonn (2):
openrisc: include export.h for EXPORT_SYMBOL
openrisc: Fix up audit_syscall_[entry|exit]() usage
arch/openrisc/include/asm/ptrace.h | 8 +++++++-
arch/openrisc/kernel/init_task.c | 1 +
arch/openrisc/kernel/irq.c | 1 +
arch/openrisc/kernel/ptrace.c | 12 ++++--------
4 files changed, 13 insertions(+), 9 deletions(-)
reply other threads:[~2012-02-29 9:30 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=1330507800.2964.52.camel@crucifix \
--to=jonas@southpole.se \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®