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.6-rc1
Date: Tue, 5 Sep 2023 16:59:43 +0200 [thread overview]
Message-ID: <6d8d829b-0ca5-8f8c-8b62-a9736b26b586@monstr.eu> (raw)
Hi Linus,
please pull these 3 patches to your tree. There should be other patches for
Microblaze to go through Andrew's tree.
Thanks,
Michal
The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5:
Linux 6.5-rc1 (2023-07-09 13:53:13 -0700)
are available in the Git repository at:
git://git.monstr.eu/linux-2.6-microblaze.git tags/microblaze-v6.6
for you to fetch changes up to 0d2b49479bf91c857d83608da7b64328e556dff7:
microblaze: Make virt_to_pfn() a static inline (2023-08-23 09:35:22 +0200)
----------------------------------------------------------------
Microblaze patches for 6.6-rc1
- Cleanup DT headers
- Remove unused zalloc_maybe_bootmem()
- Make virt_to_pfn() a static inline
----------------------------------------------------------------
Christophe Leroy (1):
microblaze: Remove zalloc_maybe_bootmem()
Linus Walleij (1):
microblaze: Make virt_to_pfn() a static inline
Rob Herring (1):
microblaze: Explicitly include correct DT includes
arch/microblaze/include/asm/page.h | 27 ++++++++++++++------
arch/microblaze/include/asm/setup.h | 2 --
arch/microblaze/kernel/reset.c | 1 -
arch/microblaze/mm/init.c | 16 ------------
4 files changed, 19 insertions(+), 27 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:[~2023-09-05 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 14:59 Michal Simek [this message]
2023-09-05 19:42 ` 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=6d8d829b-0ca5-8f8c-8b62-a9736b26b586@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®