From: Stafford Horne <shorne@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Openrisc <openrisc@lists.librecores.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] OpenRISC updates for 5.17
Date: Fri, 14 Jan 2022 22:07:18 +0900 [thread overview]
Message-ID: <YeF1hpMbYo5PMmkD@antec> (raw)
Hi Linus,
Please consider for pull
The following changes since commit d58071a8a76d779eedab38033ae4c821c30295a5:
Linux 5.16-rc3 (2021-11-28 14:09:19 -0800)
are available in the Git repository at:
git://github.com/openrisc/linux.git tags/for-linus
for you to fetch changes up to 7f435e42fd6b65fd8759963156e1ef0fb7d213f8:
openrisc: init: Add support for common clk (2022-01-12 06:13:22 +0900)
----------------------------------------------------------------
OpenRISC updates for 5.17
A few fixups and enhancements for OpenRISC:
- Fix to add proper wrapper for clone3 to save callee saved regs
- Cleanups for clone, fork and switch
- Add support for common clk so OpenRISC and use more drivers
----------------------------------------------------------------
Stafford Horne (4):
openrisc: Cleanup switch code and comments
openrisc: Use delay slot for clone and fork wrappers
openrisc: Add clone3 ABI wrapper
openrisc: init: Add support for common clk
arch/openrisc/Kconfig | 1 +
arch/openrisc/include/asm/syscalls.h | 2 ++
arch/openrisc/kernel/entry.S | 27 +++++++++++++--------------
arch/openrisc/kernel/time.c | 4 ++++
4 files changed, 20 insertions(+), 14 deletions(-)
next reply other threads:[~2022-01-14 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 13:07 Stafford Horne [this message]
2022-01-14 14:39 ` [GIT PULL] OpenRISC updates for 5.17 pr-tracker-bot
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=YeF1hpMbYo5PMmkD@antec \
--to=shorne@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openrisc@lists.librecores.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