From: Michal Simek <monstr@monstr.eu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] arch/microblaze fixes for 4.16-rc6
Date: Fri, 16 Mar 2018 12:55:28 +0100 [thread overview]
Message-ID: <b30cd129-e617-ffe8-18a6-127d558a1abd@monstr.eu> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1538 bytes --]
Hi,
please pull the following fixes to your tree to fix current issues.
Thanks,
Michal
The following changes since commit 91ab883eb21325ad80f3473633f794c78ac87f51:
Linux 4.16-rc2 (2018-02-18 17:29:42 -0800)
are available in the git repository at:
git://git.monstr.eu/linux-2.6-microblaze.git tags/microblaze-4.16-rc6
for you to fetch changes up to 101646a24a2f9cdb61d7732459fbf068a7bbb542:
microblaze: switch to NO_BOOTMEM (2018-03-16 12:51:27 +0100)
----------------------------------------------------------------
Microblaze fixes for 4.16-rc6
- Use NO_BOOTMEM to fix boot issue
- Fix opt lib endian dependencies
----------------------------------------------------------------
Michal Simek (1):
microblaze: Setup dependencies for ASM optimized lib functions
Rob Herring (2):
microblaze: remove unused alloc_maybe_bootmem
microblaze: switch to NO_BOOTMEM
arch/microblaze/Kconfig | 1 +
arch/microblaze/Kconfig.platform | 2 +-
arch/microblaze/include/asm/setup.h | 1 -
arch/microblaze/lib/fastcopy.S | 4 ----
arch/microblaze/mm/init.c | 64
++++++-------------------------------------------------
5 files changed, 8 insertions(+), 64 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 SoCs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2018-03-16 11:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b30cd129-e617-ffe8-18a6-127d558a1abd@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®