From: Michal Simek <monstr@monstr.eu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] arch/microblaze patches for 6.13-rc1
Date: Tue, 19 Nov 2024 08:05:42 +0100 [thread overview]
Message-ID: <39293bc3-ad14-4196-8a25-a13d66982b2f@monstr.eu> (raw)
Hi Linus,
please pull these 3 simple patches to your tree.
Thanks,
Michal
The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:
Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)
are available in the Git repository at:
git://git.monstr.eu/linux-2.6-microblaze.git tags/microblaze-v6.13
for you to fetch changes up to eb01f8f3c446ed81e3b2c44b7fbed8a5d6be9d3d:
microblaze: mb: Use str_yes_no() helper in show_cpuinfo() (2024-11-15
10:27:48 +0100)
----------------------------------------------------------------
Microblaze patches for 6.13-rc1
- Export xmb_manager functions
- Remove empty #ifndef __ASSEMBLY__ statement
- Use str_yes_no() helper in show_cpuinfo()
----------------------------------------------------------------
Michal Simek (1):
microblaze: Export xmb_manager functions
Thomas Huth (1):
microblaze: Remove empty #ifndef __ASSEMBLY__ statement
Thorsten Blum (1):
microblaze: mb: Use str_yes_no() helper in show_cpuinfo()
arch/microblaze/include/uapi/asm/setup.h | 3 ---
arch/microblaze/kernel/cpu/mb.c | 10 +++++-----
arch/microblaze/kernel/microblaze_ksyms.c | 10 ++++++++++
3 files changed, 15 insertions(+), 8 deletions(-)
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP/Versal ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal/Versal NET SoCs
TF-A maintainer - Xilinx ZynqMP/Versal/Versal NET SoCs
next reply other threads:[~2024-11-19 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 7:05 Michal Simek [this message]
2024-11-20 23:02 ` 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=39293bc3-ad14-4196-8a25-a13d66982b2f@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®