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 fixes for 6.13-rc3
Date: Thu, 12 Dec 2024 16:49:15 +0000 [thread overview]
Message-ID: <Z1sUC4d1kUipZIy1@antec> (raw)
Hello Linus,
Please consider for pull,
The following changes since commit fac04efc5c793dccbd07e2d59af9f90b7fc0dca4:
Linux 6.13-rc2 (2024-12-08 14:03:39 -0800)
are available in the Git repository at:
https://github.com/openrisc/linux.git tags/for-linus
for you to fetch changes up to c8f8d4344d50d72181207ee73175bba567c25f58:
openrisc: Fix misalignments in head.S (2024-12-10 12:04:19 +0000)
----------------------------------------------------------------
OpenRISC fixes for 6.13-rc3
A few fixes. One is just a formatting change but I figure I will include
it here to avoid unnessesary pull requests in the future. If you prefer
not to merge it now I can leave it out.
- Fix from Masahiro Yamada to fix 6.13 OpenRISC boot issues after
vmlinux.lds.h symbol ordering was changed.
- Code formatting fixups from Geert.
----------------------------------------------------------------
Geert Uytterhoeven (1):
openrisc: Fix misalignments in head.S
Masahiro Yamada (1):
openrisc: place exception table at the head of vmlinux
arch/openrisc/kernel/entry.S | 2 ++
arch/openrisc/kernel/head.S | 32 +++++++++++++++++---------------
arch/openrisc/kernel/vmlinux.lds.S | 3 +--
scripts/head-object-list.txt | 1 -
4 files changed, 20 insertions(+), 18 deletions(-)
next reply other threads:[~2024-12-12 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 16:49 Stafford Horne [this message]
2024-12-12 21:27 ` [GIT PULL] OpenRISC fixes for 6.13-rc3 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=Z1sUC4d1kUipZIy1@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 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).