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 5.18-rc1
Date: Mon, 28 Mar 2022 14:10:56 +0200 [thread overview]
Message-ID: <04dd8f40-84eb-2c31-5b16-33ac60024b7f@monstr.eu> (raw)
Hi Linus,
please pull these 3 simple patches.
Thanks,
Michal
The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:
Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)
are available in the Git repository at:
git://git.monstr.eu/linux-2.6-microblaze.git tags/microblaze-v5.18
for you to fetch changes up to fcc619621df50f63b641b18536f908b05d6782a4:
microblaze/PCI: Remove pci_phys_mem_access_prot() dead code (2022-01-24
13:11:34 +0100)
----------------------------------------------------------------
Microblaze patches for 5.18-rc1
- Small fixups
- Remove unused pci_phys_mem_access_prot()
----------------------------------------------------------------
Bjorn Helgaas (1):
microblaze/PCI: Remove pci_phys_mem_access_prot() dead code
Jason Wang (1):
microblaze: fix typo in a comment
Xiang wangx (1):
microblaze: add const to of_device_id
arch/microblaze/include/asm/pci.h | 4 --
arch/microblaze/kernel/signal.c | 2 +-
arch/microblaze/pci/pci-common.c | 49 --------------------
arch/microblaze/pci/xilinx_pci.c | 2 +-
4 files changed, 2 insertions(+), 55 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 ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
next reply other threads:[~2022-03-28 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 12:10 Michal Simek [this message]
2022-03-28 22:06 ` 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=04dd8f40-84eb-2c31-5b16-33ac60024b7f@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®