From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [GIT PULL] OpenRISC updates for 5.18
Date: Sun, 27 Mar 2022 16:30:00 +0900 [thread overview]
Message-ID: <YkASeMlP+k/OJm3+@antec> (raw)
Hi Linus,
Not much for OpenRISC this merge window, I do have some things on the back
burner like sparse warning cleanups and new defconfigs. But I didn't get time
to polish the patches off for this round. There are OpenRISC updates coming in
via other queues like removal of set_fs() and possibly new generic ticket locks.
With that said please consider for pull:
The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:
Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)
are available in the Git repository at:
git at github.com:openrisc/linux.git tags/for-linus
for you to fetch changes up to 862cf8d5fd98ed8ea8989726ed5da53761a9ed76:
openrisc/boot: Remove unnecessary initialisation in memcpy(). (2022-01-30 17:44:34 +0900)
----------------------------------------------------------------
OpenRISC updates for 5.18
Fixups and enhancements for OpenRISC:
- Small fixup to remove duplicate initializer in memcpy from Kuniyuki
Iwashima
----------------------------------------------------------------
Kuniyuki Iwashima (1):
openrisc/boot: Remove unnecessary initialisation in memcpy().
arch/openrisc/lib/memcpy.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2022-03-27 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 7:30 Stafford Horne [this message]
2022-03-27 19:33 ` [OpenRISC] [GIT PULL] OpenRISC updates for 5.18 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=YkASeMlP+k/OJm3+@antec \
--to=shorne@gmail.com \
--cc=openrisc@lists.librecores.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;
as well as URLs for NNTP newsgroup(s).