From: Jonas Bonn <jonas@southpole.se>
To: viro@zeniv.linux.org.uk
Cc: linux-kernel@vger.kernel.org, Jonas Bonn <jonas@southpole.se>
Subject: [PATCH 0/2] openrisc: more kernel_thread cleanup
Date: Thu, 25 Oct 2012 17:46:37 +0200 [thread overview]
Message-ID: <1351179999-8376-1-git-send-email-jonas@southpole.se> (raw)
Hi Al,
A couple of patches here that continue the cleanup outlined in the
kernel_thread discussion. Feel free to take these via your tree if
you feel that's appropriate; otherwise let me know and I'll throw
these into the openrisc tree.
/Jonas
Jonas Bonn (2):
openrisc: move sys_clone's stack determination to copy_thread
openrisc: determine regs directly in copy_thread
arch/openrisc/kernel/entry.S | 6 ++----
arch/openrisc/kernel/process.c | 9 +++++++--
arch/openrisc/kernel/sys_or32.c | 15 ++++-----------
3 files changed, 13 insertions(+), 17 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-10-25 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 15:46 Jonas Bonn [this message]
2012-10-25 15:46 ` [PATCH 1/2] openrisc: move sys_clone's stack determination to copy_thread Jonas Bonn
2012-10-25 15:55 ` Al Viro
2012-10-25 16:16 ` Jonas Bonn
2012-10-25 15:46 ` [PATCH 2/2] openrisc: determine regs directly in copy_thread Jonas Bonn
2012-10-25 16:27 ` Al Viro
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=1351179999-8376-1-git-send-email-jonas@southpole.se \
--to=jonas@southpole.se \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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®