mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 patches for 5.6-rc1
Date: Tue, 4 Feb 2020 12:08:25 +0100	[thread overview]
Message-ID: <92cc6617-e2c3-e3b8-cf20-c8ccf748d37a@monstr.eu> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2415 bytes --]

Hi Linus,

please pull the following patches to your tree. I have also including my
patch for dma-contiguous.h suggested by Christoph and acked by others
with Microblaze CMA wiring.

Thanks,
Michal


The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:

  Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)

are available in the Git repository at:

  git://git.monstr.eu/linux-2.6-microblaze.git tags/microblaze-v5.6-rc1

for you to fetch changes up to 6aa71ef9bcf9d8688c777dfbff340348cb89a5b4:

  microblaze: Add ID for Microblaze v11 (2020-02-04 11:38:59 +0100)

----------------------------------------------------------------
Microblaze patches for 5.6-rc1

- Enable CMA
- Add support for MB v11
- Defconfig updates
- Minor fixes

----------------------------------------------------------------
Manish Narani (1):
      microblaze: defconfig: Disable EXT2 driver and Enable EXT3 & EXT4
drivers

Michal Simek (5):
      microblaze: Align comments with register usage
      microblaze: Sync defconfig with latest Kconfig layout
      asm-generic: Make dma-contiguous.h a mandatory include/asm header
      microblaze: Wire CMA allocator
      microblaze: Add ID for Microblaze v11

Shubhrajyoti Datta (1):
      microblaze: Prevent the overflow of the start

 arch/arm64/include/asm/Kbuild           |  1 -
 arch/csky/include/asm/Kbuild            |  1 -
 arch/microblaze/Kconfig                 |  1 +
 arch/microblaze/configs/mmu_defconfig   | 10 ++++++----
 arch/microblaze/configs/nommu_defconfig |  2 +-
 arch/microblaze/kernel/cpu/cache.c      |  3 ++-
 arch/microblaze/kernel/cpu/cpuinfo.c    |  1 +
 arch/microblaze/kernel/head.S           |  8 ++++----
 arch/microblaze/mm/init.c               |  4 ++++
 arch/mips/include/asm/Kbuild            |  1 -
 arch/riscv/include/asm/Kbuild           |  1 -
 arch/s390/include/asm/Kbuild            |  1 -
 arch/x86/include/asm/Kbuild             |  1 -
 arch/xtensa/include/asm/Kbuild          |  1 -
 include/asm-generic/Kbuild              |  1 +
 15 files changed, 20 insertions(+), 17 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



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

             reply	other threads:[~2020-02-04 11:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 11:08 Michal Simek [this message]
2020-02-04 13:22 ` Linus Torvalds
2020-02-04 17:37   ` Michal Simek
2020-02-04 22:04     ` Linus Torvalds
2020-02-04 13:25 ` 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=92cc6617-e2c3-e3b8-cf20-c8ccf748d37a@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®