public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Gordeev <agordeev@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>
Subject: [GIT PULL] s390 updates for 6.1-rc5
Date: Fri, 11 Nov 2022 20:45:17 +0100	[thread overview]
Message-ID: <Y26mTTsPtdaNJ4lP@tuxmaker.boeblingen.de.ibm.com> (raw)

Hello Linus,

please pull s390 changes for 6.1-rc5.

Thank you,
Alexander

The following changes since commit e38de4804421b064a9c73c5a9b7f3df96b863e4b:

  s390/vfio-ap: Fix memory allocation for mdev_types array (2022-10-21 10:50:02 -0400)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-6.1-4

for you to fetch changes up to 30d17fac6aaedb40d111bb159f4b35525637ea78:

  scripts/min-tool-version.sh: raise minimum clang version to 15.0.0 for s390 (2022-10-31 13:34:56 +0100)

----------------------------------------------------------------
s390 updates for 6.1-rc5

- fix memcpy warning about field-spanning write in zcrypt driver.

- minor updates to defconfigs.

- Remove CONFIG_DEBUG_INFO_BTF from all defconfigs and add btf.config
  addon config file. It significantly decreases compile time and allows
  quickly enabling that option into the current kernel config.

- Add kasan.config addon config file which allows to easily enable
  KASAN into the current kernel config.

- binutils commit 906f69cf65da ("IBM zSystems: Issue error for *DBL
  relocs on misaligned symbols") caused several link errors.
  Always build relocatable kernel to avoid this problem.

- Raise the minimum clang version to 15.0.0 to avoid silent generation
  of a corrupted code.

----------------------------------------------------------------
Harald Freudenberger (1):
  s390/zcrypt: fix warning about field-spanning write

Heiko Carstens (5):
  s390: update defconfigs
  s390/configs: move CONFIG_DEBUG_INFO_BTF into btf.config addon config
  s390/configs: add kasan.config addon config file
  s390: always build relocatable kernel
  scripts/min-tool-version.sh: raise minimum clang version to 15.0.0 for
    s390

 arch/s390/Kconfig                     |  6 +--
 arch/s390/Makefile                    |  2 -
 arch/s390/boot/Makefile               |  3 +-
 arch/s390/boot/startup.c              |  3 +-
 arch/s390/configs/btf.config          |  1 +
 arch/s390/configs/debug_defconfig     | 65 +++++++++++++-------------
 arch/s390/configs/defconfig           | 67 +++++++++++++--------------
 arch/s390/configs/kasan.config        |  3 ++
 arch/s390/configs/zfcpdump_defconfig  |  1 -
 drivers/s390/crypto/zcrypt_msgtype6.c | 21 ++++++---
 scripts/min-tool-version.sh           |  2 +-
 11 files changed, 90 insertions(+), 84 deletions(-)
 create mode 100644 arch/s390/configs/btf.config
 create mode 100644 arch/s390/configs/kasan.config

             reply	other threads:[~2022-11-11 19:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 19:45 Alexander Gordeev [this message]
2022-11-11 19:54 ` [GIT PULL] s390 updates for 6.1-rc5 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=Y26mTTsPtdaNJ4lP@tuxmaker.boeblingen.de.ibm.com \
    --to=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@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