All of lore.kernel.org
 help / color / mirror / Atom feed
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 7.3 updates
Date: Sat, 29 Aug 2026 07:40:25 +0100	[thread overview]
Message-ID: <apJ-2fH66_goKXF0@antec> (raw)

Hello Linus,

Please consider for pull,

The following changes since commit db2ddb87143519e20a95aa36c60b36107b736a58:

  Linux 7.2-rc7 (2026-08-09 14:54:50 -0700)

are available in the Git repository at:

  https://github.com/openrisc/linux.git tags/for-linus

for you to fetch changes up to 78004e9a87f240df03e2f73120d291763c32e0a7:

  openrisc: fix arbitrary kernel memory access via or1k_atomic syscall (2026-08-29 07:32:26 +0100)

----------------------------------------------------------------
OpenRISC 7.3 updates

One small item and one bug fix.

 * The bug fix is to fix an unchecked access in our or1k_atomic syscall,
   I am debating if we should just deprecate this as there is minimal
   need for it.

----------------------------------------------------------------
Ali Ahmet Memis (1):
      openrisc: fix arbitrary kernel memory access via or1k_atomic syscall

Julia Lawall (1):
      openrisc: drop unneeded semicolon

 arch/openrisc/kernel/entry.S | 43 +++++++++++++++++++++++++++++++++++++++----
 arch/openrisc/mm/tlb.c       |  4 ++--
 2 files changed, 41 insertions(+), 6 deletions(-)

             reply	other threads:[~2026-08-29  6:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-29  6:40 Stafford Horne [this message]
2026-08-30 17:23 ` [GIT PULL] OpenRISC 7.3 updates 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=apJ-2fH66_goKXF0@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.