From: Stafford Horne <shorne@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux OpenRISC <linux-openrisc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] OpenRISC updates for 7.2
Date: Sat, 20 Jun 2026 07:08:12 +0100 [thread overview]
Message-ID: <ajYuTOzdrCbV8NM3@antec> (raw)
Hello Linus,
I just noticed, this series was done on top of a random merge during v7.0.
Please let me know if you would like to rebase on 7.1 etc, but I think it will
not change much, it's been in next for a while.
Please consider for pull,
The following changes since commit d79526b89571ae447c1a5cfd3d627efa07098348:
Merge tag 'spi-fix-v7.0-merge-window' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi (2026-02-20 17:14:36 -0800)
are available in the Git repository at:
https://github.com/openrisc/linux.git tags/for-linus
for you to fetch changes up to aca063c9024522e4e5b9a9d1927433f6a01785a3:
openrisc: Fix jump_label smp syncing (2026-05-23 06:34:49 +0100)
----------------------------------------------------------------
OpenRISC updates for 7.2
A few fixes for text patching related code:
* Update the section of map_page used in text patching. It was
left with __init when text patching was introduced to OpenRISC.
* Add fix to invalidate remote SMP core i-caches after text is patched.
----------------------------------------------------------------
Stafford Horne (4):
openrisc: mm: Fix section mismatch between map_page and __set_fixmap
openrisc: Cache invalidation cleanup
openrisc: Add full instruction cache invalidate functions
openrisc: Fix jump_label smp syncing
arch/openrisc/include/asm/cacheflush.h | 4 ++++
arch/openrisc/kernel/head.S | 10 ----------
arch/openrisc/kernel/jump_label.c | 2 +-
arch/openrisc/kernel/patching.c | 3 +++
arch/openrisc/kernel/smp.c | 21 +++++++++++++++++++++
arch/openrisc/mm/cache.c | 16 ++++++++++++++++
arch/openrisc/mm/init.c | 2 +-
7 files changed, 46 insertions(+), 12 deletions(-)
reply other threads:[~2026-06-20 6:08 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=ajYuTOzdrCbV8NM3@antec \
--to=shorne@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.