February 2021 - kernel - Fedora mailing-lists

[OS-BUILD PATCH] Add gcc-c++ to BuildRequires
by GitLab Bridge on behalf of jmflinuxtx 20 Dec '22

20 Dec '22

From: "Justin M. Forbes" <jforbes(a)fedoraproject.org> This is required for some of the gcc plugins. Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org> --- redhat/kernel.spec.template | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template index 5941924711d4..c8ee1f82c494 100755 --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -501,7 +501,7 @@ Requires: kernel-modules-uname-r = %{KVERREL}%{?variant} # BuildRequires: kmod, patch, bash, tar, git-core BuildRequires: bzip2, xz, findutils, gzip, m4, perl-interpreter, perl-Carp, perl-devel, perl-generators, make, diffutils, gawk -BuildRequires: gcc, binutils, redhat-rpm-config, hmaccalc, bison, flex +BuildRequires: gcc, binutils, redhat-rpm-config, hmaccalc, bison, flex, gcc-c++ BuildRequires: net-tools, hostname, bc, elfutils-devel BuildRequires: dwarves BuildRequires: python3-devel -- GitLab

4 3

[OS-BUILD PATCH] [redhat] New configs in drivers/net/usb
by GitLab Bridge on behalf of redhat-patchlab 19 Jun '21

19 Jun '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_USB_RTL8153_ECM: This option supports ECM mode for RTL8153 ethernet adapter, when CONFIG_USB_RTL8152 is not set, or the RTL8153 device is not supported by r8152 driver. Symbol: USB_RTL8153_ECM [=m] Type : tristate Defined at drivers/net/usb/Kconfig:631 Prompt: RTL8153 ECM support Depends on: NETDEVICES [=y] && USB_NET_DRIVERS [=y] && USB_NET_CDCETHER [=m] && (USB_RTL8152 [=m] || USB_RTL8152 [=m]=n) Location: -> Device Drivers -> Network device support (NETDEVICES [=y]) -> USB Network Adapters (USB_NET_DRIVERS [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_USB_RTL8153_ECM | 1 + .../generic/CONFIG_USB_RTL8153_ECM | 19 ------------------- 2 files changed, 1 insertion(+), 19 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_USB_RTL8153_ECM delete mode 100644 redhat/configs/pending-common/generic/CONFIG_USB_RTL8153_ECM diff --git a/redhat/configs/common/generic/CONFIG_USB_RTL8153_ECM b/redhat/configs/common/generic/CONFIG_USB_RTL8153_ECM new file mode 100644 index 000000000000..3ec37682be5c --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_USB_RTL8153_ECM @@ -0,0 +1 @@ +CONFIG_USB_RTL8153_ECM=m diff --git a/redhat/configs/pending-common/generic/CONFIG_USB_RTL8153_ECM b/redhat/configs/pending-common/generic/CONFIG_USB_RTL8153_ECM deleted file mode 100644 index 2aac1c66d354..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_USB_RTL8153_ECM +++ /dev/null @@ -1,19 +0,0 @@ -# CONFIG_USB_RTL8153_ECM: -# -# This option supports ECM mode for RTL8153 ethernet adapter, when -# CONFIG_USB_RTL8152 is not set, or the RTL8153 device is not -# supported by r8152 driver. -# -# Symbol: USB_RTL8153_ECM [=m] -# Type : tristate -# Defined at drivers/net/usb/Kconfig:631 -# Prompt: RTL8153 ECM support -# Depends on: NETDEVICES [=y] && USB_NET_DRIVERS [=y] && USB_NET_CDCETHER [=m] && (USB_RTL8152 [=m] || USB_RTL8152 [=m]=n) -# Location: -# -> Device Drivers -# -> Network device support (NETDEVICES [=y]) -# -> USB Network Adapters (USB_NET_DRIVERS [=y]) -# -# -# -CONFIG_USB_RTL8153_ECM=m -- GitLab

4 5

[OS-BUILD PATCH] [redhat] New configs in drivers/extcon
by GitLab Bridge on behalf of redhat-patchlab 19 Jun '21

19 Jun '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_EXTCON_USBC_TUSB320: Say Y here to enable support for USB Type C cable detection extcon support using a TUSB320. Symbol: EXTCON_USBC_TUSB320 [=n] Type : tristate Defined at drivers/extcon/Kconfig:189 Prompt: TI TUSB320 USB-C extcon support Depends on: EXTCON [=y] && I2C [=y] Location: -> Device Drivers -> External Connector Class (extcon) support (EXTCON [=y]) Selects: REGMAP_I2C [=m] --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_EXTCON_USBC_TUSB320 | 1 + .../generic/CONFIG_EXTCON_USBC_TUSB320 | 18 ------------------ 2 files changed, 1 insertion(+), 18 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_EXTCON_USBC_TUSB320 delete mode 100644 redhat/configs/pending-common/generic/CONFIG_EXTCON_USBC_TUSB320 diff --git a/redhat/configs/common/generic/CONFIG_EXTCON_USBC_TUSB320 b/redhat/configs/common/generic/CONFIG_EXTCON_USBC_TUSB320 new file mode 100644 index 000000000000..4eedae83091b --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_EXTCON_USBC_TUSB320 @@ -0,0 +1 @@ +# CONFIG_EXTCON_USBC_TUSB320 is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_EXTCON_USBC_TUSB320 b/redhat/configs/pending-common/generic/CONFIG_EXTCON_USBC_TUSB320 deleted file mode 100644 index 74b8e5ac1d0d..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_EXTCON_USBC_TUSB320 +++ /dev/null @@ -1,18 +0,0 @@ -# CONFIG_EXTCON_USBC_TUSB320: -# -# Say Y here to enable support for USB Type C cable detection extcon -# support using a TUSB320. -# -# Symbol: EXTCON_USBC_TUSB320 [=n] -# Type : tristate -# Defined at drivers/extcon/Kconfig:189 -# Prompt: TI TUSB320 USB-C extcon support -# Depends on: EXTCON [=y] && I2C [=y] -# Location: -# -> Device Drivers -# -> External Connector Class (extcon) support (EXTCON [=y]) -# Selects: REGMAP_I2C [=m] -# -# -# -# CONFIG_EXTCON_USBC_TUSB320 is not set -- GitLab

4 5

[OS-BUILD PATCH] [redhat] New configs in drivers/pwm
by GitLab Bridge on behalf of redhat-patchlab 19 Jun '21

19 Jun '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_PWM_ATMEL_TCB: Generic PWM framework driver for Atmel Timer Counter Block. A Timer Counter Block provides 6 PWM devices grouped by 2. Devices in a given group must have the same period. To compile this driver as a module, choose M here: the module will be called pwm-atmel-tcb. Symbol: PWM_ATMEL_TCB [=n] Type : tristate Defined at drivers/pwm/Kconfig:76 Prompt: Atmel TC Block PWM support Depends on: PWM [=y] && OF [=y] Location: -> Device Drivers -> Pulse-Width Modulation (PWM) Support (PWM [=y]) Selects: REGMAP_MMIO [=n] --- CONFIG_PWM_DWC: PWM driver for Synopsys DWC PWM Controller attached to a PCI bus. To compile this driver as a module, choose M here: the module will be called pwm-dwc. Symbol: PWM_DWC [=n] Type : tristate Defined at drivers/pwm/Kconfig:167 Prompt: DesignWare PWM Controller Depends on: PWM [=y] && PCI [=y] Location: -> Device Drivers -> Pulse-Width Modulation (PWM) Support (PWM [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_PWM_ATMEL_TCB | 1 + redhat/configs/common/generic/CONFIG_PWM_DWC | 1 + .../generic/CONFIG_PWM_ATMEL_TCB | 23 ------------------- .../pending-common/generic/CONFIG_PWM_DWC | 19 --------------- 4 files changed, 2 insertions(+), 42 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_PWM_ATMEL_TCB create mode 100644 redhat/configs/common/generic/CONFIG_PWM_DWC delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PWM_ATMEL_TCB delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PWM_DWC diff --git a/redhat/configs/common/generic/CONFIG_PWM_ATMEL_TCB b/redhat/configs/common/generic/CONFIG_PWM_ATMEL_TCB new file mode 100644 index 000000000000..0b75af7f9d88 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_PWM_ATMEL_TCB @@ -0,0 +1 @@ +# CONFIG_PWM_ATMEL_TCB is not set diff --git a/redhat/configs/common/generic/CONFIG_PWM_DWC b/redhat/configs/common/generic/CONFIG_PWM_DWC new file mode 100644 index 000000000000..8aea5b09615e --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_PWM_DWC @@ -0,0 +1 @@ +# CONFIG_PWM_DWC is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_PWM_ATMEL_TCB b/redhat/configs/pending-common/generic/CONFIG_PWM_ATMEL_TCB deleted file mode 100644 index 661d0650fdc2..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_PWM_ATMEL_TCB +++ /dev/null @@ -1,23 +0,0 @@ -# CONFIG_PWM_ATMEL_TCB: -# -# Generic PWM framework driver for Atmel Timer Counter Block. -# -# A Timer Counter Block provides 6 PWM devices grouped by 2. -# Devices in a given group must have the same period. -# -# To compile this driver as a module, choose M here: the module -# will be called pwm-atmel-tcb. -# -# Symbol: PWM_ATMEL_TCB [=n] -# Type : tristate -# Defined at drivers/pwm/Kconfig:76 -# Prompt: Atmel TC Block PWM support -# Depends on: PWM [=y] && OF [=y] -# Location: -# -> Device Drivers -# -> Pulse-Width Modulation (PWM) Support (PWM [=y]) -# Selects: REGMAP_MMIO [=n] -# -# -# -# CONFIG_PWM_ATMEL_TCB is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_PWM_DWC b/redhat/configs/pending-common/generic/CONFIG_PWM_DWC deleted file mode 100644 index 34314ebef8b7..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_PWM_DWC +++ /dev/null @@ -1,19 +0,0 @@ -# CONFIG_PWM_DWC: -# -# PWM driver for Synopsys DWC PWM Controller attached to a PCI bus. -# -# To compile this driver as a module, choose M here: the module -# will be called pwm-dwc. -# -# Symbol: PWM_DWC [=n] -# Type : tristate -# Defined at drivers/pwm/Kconfig:167 -# Prompt: DesignWare PWM Controller -# Depends on: PWM [=y] && PCI [=y] -# Location: -# -> Device Drivers -# -> Pulse-Width Modulation (PWM) Support (PWM [=y]) -# -# -# -# CONFIG_PWM_DWC is not set -- GitLab

3 3

[OS-BUILD PATCH] [redhat] New configs in drivers/mtd
by GitLab Bridge on behalf of redhat-patchlab 19 Jun '21

19 Jun '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_MTD_NAND_ECC_SW_BCH: This enables support for software BCH error correction. Binary BCH codes are more powerful and cpu intensive than traditional Hamming ECC codes. They are used with NAND devices requiring more than 1 bit of error correction. Symbol: MTD_NAND_ECC_SW_BCH [=n] Type : bool Defined at drivers/mtd/nand/Kconfig:38 Prompt: Software BCH ECC engine Depends on: MTD [=m] Location: -> Device Drivers -> Memory Technology Device (MTD) support (MTD [=m]) -> NAND -> ECC engine support Selects: BCH [=n] && MTD_NAND_ECC [=n] --- CONFIG_MTD_NAND_ECC_SW_HAMMING: This enables support for software Hamming error correction. This correction can correct up to 1 bit error per chunk and detect up to 2 bit errors. While it used to be widely used with old parts, newer NAND chips usually require more strength correction and in this case BCH or RS will be preferred. Symbol: MTD_NAND_ECC_SW_HAMMING [=n] Type : bool Defined at drivers/mtd/nand/Kconfig:18 Prompt: Software Hamming ECC engine Depends on: MTD [=m] Location: -> Device Drivers -> Memory Technology Device (MTD) support (MTD [=m]) -> NAND -> ECC engine support Selects: MTD_NAND_ECC [=n] Selected by [n]: - SM_FTL [=n] && MTD [=m] && BLOCK [=y] - MTD_NAND_NDFC [=n] && MTD [=m] && MTD_RAW_NAND [=n] && 4xx --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_MTD_NAND_ECC_SW_BCH | 1 + .../generic/CONFIG_MTD_NAND_ECC_SW_HAMMING | 1 + .../generic/CONFIG_MTD_NAND_ECC_SW_BCH | 22 --------------- .../generic/CONFIG_MTD_NAND_ECC_SW_HAMMING | 27 ------------------- 4 files changed, 2 insertions(+), 49 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_MTD_NAND_ECC_SW_BCH create mode 100644 redhat/configs/common/generic/CONFIG_MTD_NAND_ECC_SW_HAMMING delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MTD_NAND_ECC_SW_BCH delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MTD_NAND_ECC_SW_HAMMING diff --git a/redhat/configs/common/generic/CONFIG_MTD_NAND_ECC_SW_BCH b/redhat/configs/common/generic/CONFIG_MTD_NAND_ECC_SW_BCH new file mode 100644 index 000000000000..68691d93530a --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_MTD_NAND_ECC_SW_BCH @@ -0,0 +1 @@ +# CONFIG_MTD_NAND_ECC_SW_BCH is not set diff --git a/redhat/configs/common/generic/CONFIG_MTD_NAND_ECC_SW_HAMMING b/redhat/configs/common/generic/CONFIG_MTD_NAND_ECC_SW_HAMMING new file mode 100644 index 000000000000..81d0f3e93ba8 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_MTD_NAND_ECC_SW_HAMMING @@ -0,0 +1 @@ +# CONFIG_MTD_NAND_ECC_SW_HAMMING is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_MTD_NAND_ECC_SW_BCH b/redhat/configs/pending-common/generic/CONFIG_MTD_NAND_ECC_SW_BCH deleted file mode 100644 index a59a866326ba..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_MTD_NAND_ECC_SW_BCH +++ /dev/null @@ -1,22 +0,0 @@ -# CONFIG_MTD_NAND_ECC_SW_BCH: -# -# This enables support for software BCH error correction. Binary BCH -# codes are more powerful and cpu intensive than traditional Hamming -# ECC codes. They are used with NAND devices requiring more than 1 bit -# of error correction. -# -# Symbol: MTD_NAND_ECC_SW_BCH [=n] -# Type : bool -# Defined at drivers/mtd/nand/Kconfig:38 -# Prompt: Software BCH ECC engine -# Depends on: MTD [=m] -# Location: -# -> Device Drivers -# -> Memory Technology Device (MTD) support (MTD [=m]) -# -> NAND -# -> ECC engine support -# Selects: BCH [=n] && MTD_NAND_ECC [=n] -# -# -# -# CONFIG_MTD_NAND_ECC_SW_BCH is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_MTD_NAND_ECC_SW_HAMMING b/redhat/configs/pending-common/generic/CONFIG_MTD_NAND_ECC_SW_HAMMING deleted file mode 100644 index d23ac128daad..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_MTD_NAND_ECC_SW_HAMMING +++ /dev/null @@ -1,27 +0,0 @@ -# CONFIG_MTD_NAND_ECC_SW_HAMMING: -# -# This enables support for software Hamming error -# correction. This correction can correct up to 1 bit error -# per chunk and detect up to 2 bit errors. While it used to be -# widely used with old parts, newer NAND chips usually require -# more strength correction and in this case BCH or RS will be -# preferred. -# -# Symbol: MTD_NAND_ECC_SW_HAMMING [=n] -# Type : bool -# Defined at drivers/mtd/nand/Kconfig:18 -# Prompt: Software Hamming ECC engine -# Depends on: MTD [=m] -# Location: -# -> Device Drivers -# -> Memory Technology Device (MTD) support (MTD [=m]) -# -> NAND -# -> ECC engine support -# Selects: MTD_NAND_ECC [=n] -# Selected by [n]: -# - SM_FTL [=n] && MTD [=m] && BLOCK [=y] -# - MTD_NAND_NDFC [=n] && MTD [=m] && MTD_RAW_NAND [=n] && 4xx -# -# -# -# CONFIG_MTD_NAND_ECC_SW_HAMMING is not set -- GitLab

3 3

[OS-BUILD PATCH] [redhat] New configs in drivers/usb
by CKI Gitlab (via Email Bridge) 17 Jun '21

17 Jun '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/usb Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_USB_CDNS_SUPPORT: Say Y here if your system has a Cadence USBSS or USBSSP dual-role controller. It supports: dual-role switch, Host-only, and Peripheral-only. Symbol: USB_CDNS_SUPPORT [=n] Type : tristate Defined at drivers/usb/cdns3/Kconfig:1 Prompt: Cadence USB Support Depends on: USB_SUPPORT [=y] && (USB [=y] || USB_GADGET [=n]) && HAS_DMA [=y] Location: -> Device Drivers -> USB support (USB_SUPPORT [=y]) Selects: USB_XHCI_PLATFORM [=n] && USB_ROLE_SWITCH [=m] --- CONFIG_USB_SERIAL_XR: Say Y here if you want to use MaxLinear/Exar USB to Serial converter devices. To compile this driver as a module, choose M here: the module will be called xr_serial. Symbol: USB_SERIAL_XR [=n] Type : tristate Defined at drivers/usb/serial/Kconfig:636 Prompt: USB MaxLinear/Exar USB to Serial driver Depends on: USB_SUPPORT [=y] && USB [=y] && USB_SERIAL [=y] Location: -> Device Drivers -> USB support (USB_SUPPORT [=y]) -> USB Serial Converter support (USB_SERIAL [=y]) --- Cc: Torez Smith <torez(a)redhat.com> Cc: Don Zickus <dzickus(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_USB_CDNS_SUPPORT b/redhat/configs/common/generic/CONFIG_USB_CDNS_SUPPORT --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_USB_CDNS_SUPPORT @@ -0,0 +1 @@ +# CONFIG_USB_CDNS_SUPPORT is not set diff a/redhat/configs/common/generic/CONFIG_USB_SERIAL_XR b/redhat/configs/common/generic/CONFIG_USB_SERIAL_XR --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_USB_SERIAL_XR @@ -0,0 +1 @@ +# CONFIG_USB_SERIAL_XR is not set diff a/redhat/configs/pending-common/generic/CONFIG_USB_CDNS_SUPPORT b/redhat/configs/pending-common/generic/CONFIG_USB_CDNS_SUPPORT --- a/redhat/configs/pending-common/generic/CONFIG_USB_CDNS_SUPPORT +++ /dev/null @@ -1,19 +0,0 @@ -# CONFIG_USB_CDNS_SUPPORT: -# -# Say Y here if your system has a Cadence USBSS or USBSSP -# dual-role controller. -# It supports: dual-role switch, Host-only, and Peripheral-only. -# -# Symbol: USB_CDNS_SUPPORT [=n] -# Type : tristate -# Defined at drivers/usb/cdns3/Kconfig:1 -# Prompt: Cadence USB Support -# Depends on: USB_SUPPORT [=y] && (USB [=y] || USB_GADGET [=n]) && HAS_DMA [=y] -# Location: -# -> Device Drivers -# -> USB support (USB_SUPPORT [=y]) -# Selects: USB_XHCI_PLATFORM [=n] && USB_ROLE_SWITCH [=m] -# -# -# -# CONFIG_USB_CDNS_SUPPORT is not set diff a/redhat/configs/pending-common/generic/CONFIG_USB_SERIAL_XR b/redhat/configs/pending-common/generic/CONFIG_USB_SERIAL_XR --- a/redhat/configs/pending-common/generic/CONFIG_USB_SERIAL_XR +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_USB_SERIAL_XR: -# -# Say Y here if you want to use MaxLinear/Exar USB to Serial converter -# devices. -# -# To compile this driver as a module, choose M here: the -# module will be called xr_serial. -# -# Symbol: USB_SERIAL_XR [=n] -# Type : tristate -# Defined at drivers/usb/serial/Kconfig:636 -# Prompt: USB MaxLinear/Exar USB to Serial driver -# Depends on: USB_SUPPORT [=y] && USB [=y] && USB_SERIAL [=y] -# Location: -# -> Device Drivers -# -> USB support (USB_SUPPORT [=y]) -# -> USB Serial Converter support (USB_SERIAL [=y]) -# -# -# -# CONFIG_USB_SERIAL_XR is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/911

3 4

[OS-BUILD PATCH] [redhat] New configs in drivers/iio
by GitLab Bridge on behalf of jeremycline 17 Jun '21

17 Jun '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_ADXRS290: Say yes here to build support for Analog Devices ADXRS290 programmable digital output gyroscope. This driver can also be built as a module. If so, the module will be called adxrs290. Symbol: ADXRS290 [=n] Type : tristate Defined at drivers/iio/gyro/Kconfig:44 Prompt: Analog Devices ADXRS290 Dual-Axis MEMS Gyroscope SPI driver Depends on: IIO [=m] && SPI [=y] Location: -> Device Drivers -> Industrial I/O support (IIO [=m]) -> Digital gyroscope sensors Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] --- CONFIG_AS73211: If you say yes here you get support for the AMS AS73211 JENCOLOR(R) Digital XYZ Sensor. For triggered measurements, you will need an additional trigger driver like IIO_HRTIMER_TRIGGER or IIO_SYSFS_TRIGGER. This driver can also be built as a module. If so, the module will be called as73211. Symbol: AS73211 [=n] Type : tristate Defined at drivers/iio/light/Kconfig:89 Prompt: AMS AS73211 XYZ color sensor Depends on: IIO [=m] && I2C [=y] Location: -> Device Drivers -> Industrial I/O support (IIO [=m]) -> Light sensors Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] --- CONFIG_HDC2010: Say yes here to build support for the Texas Instruments HDC2010 and HDC2080 relative humidity and temperature sensors. To compile this driver as a module, choose M here: the module will be called hdc2010. Symbol: HDC2010 [=n] Type : tristate Defined at drivers/iio/humidity/Kconfig:41 Prompt: TI HDC2010 relative humidity and temperature sensor Depends on: IIO [=m] && I2C [=y] Location: -> Device Drivers -> Industrial I/O support (IIO [=m]) -> Humidity sensors --- CONFIG_IIO_BUFFER_DMA: Provides the generic IIO DMA buffer infrastructure that can be used by drivers for devices with DMA support to implement the IIO buffer. Should be selected by drivers that want to use the generic DMA buffer infrastructure. Symbol: IIO_BUFFER_DMA [=n] Type : tristate Defined at drivers/iio/buffer/Kconfig:13 Prompt: Industrial I/O DMA buffer infrastructure Depends on: IIO [=m] && IIO_BUFFER [=y] Location: -> Device Drivers -> Industrial I/O support (IIO [=m]) -> Enable buffer support within IIO (IIO_BUFFER [=y]) Selected by [n]: - IIO_BUFFER_DMAENGINE [=n] && IIO [=m] && IIO_BUFFER [=y] --- CONFIG_IIO_BUFFER_DMAENGINE: Provides a bonding of the generic IIO DMA buffer infrastructure with the DMAEngine framework. This can be used by converter drivers with a DMA port connected to an external DMA controller which is supported by the DMAEngine framework. Should be selected by drivers that want to use this functionality. Symbol: IIO_BUFFER_DMAENGINE [=n] Type : tristate Defined at drivers/iio/buffer/Kconfig:22 Prompt: Industrial I/O DMA buffer integration with DMAEngine Depends on: IIO [=m] && IIO_BUFFER [=y] Location: -> Device Drivers -> Industrial I/O support (IIO [=m]) -> Enable buffer support within IIO (IIO_BUFFER [=y]) Selects: IIO_BUFFER_DMA [=n] Selected by [n]: - ADI_AXI_ADC [=n] && IIO [=m] --- CONFIG_IIO_TRIGGERED_EVENT: Provides helper functions for setting up triggered events. Symbol: IIO_TRIGGERED_EVENT [=n] Type : tristate Defined at drivers/iio/Kconfig:65 Prompt: Enable triggered events support Depends on: IIO [=m] Location: -> Device Drivers -> Industrial I/O support (IIO [=m]) Selects: IIO_TRIGGER [=y] Selected by [n]: - HI8435 [=n] && IIO [=m] && SPI [=y] --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/common/generic/CONFIG_ADXRS290 | 1 + redhat/configs/common/generic/CONFIG_AS73211 | 1 + redhat/configs/common/generic/CONFIG_HDC2010 | 1 + .../common/generic/CONFIG_IIO_BUFFER_DMA | 1 + .../generic/CONFIG_IIO_BUFFER_DMAENGINE | 1 + .../common/generic/CONFIG_IIO_TRIGGERED_EVENT | 1 + .../pending-common/generic/CONFIG_ADXRS290 | 22 ---------------- .../pending-common/generic/CONFIG_AS73211 | 25 ------------------- .../pending-common/generic/CONFIG_HDC2010 | 21 ---------------- .../generic/CONFIG_IIO_BUFFER_DMA | 23 ----------------- .../generic/CONFIG_IIO_BUFFER_DMAENGINE | 25 ------------------- .../generic/CONFIG_IIO_TRIGGERED_EVENT | 19 -------------- 12 files changed, 6 insertions(+), 135 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_ADXRS290 create mode 100644 redhat/configs/common/generic/CONFIG_AS73211 create mode 100644 redhat/configs/common/generic/CONFIG_HDC2010 create mode 100644 redhat/configs/common/generic/CONFIG_IIO_BUFFER_DMA create mode 100644 redhat/configs/common/generic/CONFIG_IIO_BUFFER_DMAENGINE create mode 100644 redhat/configs/common/generic/CONFIG_IIO_TRIGGERED_EVENT delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ADXRS290 delete mode 100644 redhat/configs/pending-common/generic/CONFIG_AS73211 delete mode 100644 redhat/configs/pending-common/generic/CONFIG_HDC2010 delete mode 100644 redhat/configs/pending-common/generic/CONFIG_IIO_BUFFER_DMA delete mode 100644 redhat/configs/pending-common/generic/CONFIG_IIO_BUFFER_DMAENGINE delete mode 100644 redhat/configs/pending-common/generic/CONFIG_IIO_TRIGGERED_EVENT diff --git a/redhat/configs/common/generic/CONFIG_ADXRS290 b/redhat/configs/common/generic/CONFIG_ADXRS290 new file mode 100644 index 000000000000..8b7d877f13bc --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_ADXRS290 @@ -0,0 +1 @@ +# CONFIG_ADXRS290 is not set diff --git a/redhat/configs/common/generic/CONFIG_AS73211 b/redhat/configs/common/generic/CONFIG_AS73211 new file mode 100644 index 000000000000..dd3aa86a497a --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_AS73211 @@ -0,0 +1 @@ +# CONFIG_AS73211 is not set diff --git a/redhat/configs/common/generic/CONFIG_HDC2010 b/redhat/configs/common/generic/CONFIG_HDC2010 new file mode 100644 index 000000000000..fad2fecfd916 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_HDC2010 @@ -0,0 +1 @@ +# CONFIG_HDC2010 is not set diff --git a/redhat/configs/common/generic/CONFIG_IIO_BUFFER_DMA b/redhat/configs/common/generic/CONFIG_IIO_BUFFER_DMA new file mode 100644 index 000000000000..fdc2817a1429 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_IIO_BUFFER_DMA @@ -0,0 +1 @@ +# CONFIG_IIO_BUFFER_DMA is not set diff --git a/redhat/configs/common/generic/CONFIG_IIO_BUFFER_DMAENGINE b/redhat/configs/common/generic/CONFIG_IIO_BUFFER_DMAENGINE new file mode 100644 index 000000000000..7f7ca607ab89 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_IIO_BUFFER_DMAENGINE @@ -0,0 +1 @@ +# CONFIG_IIO_BUFFER_DMAENGINE is not set diff --git a/redhat/configs/common/generic/CONFIG_IIO_TRIGGERED_EVENT b/redhat/configs/common/generic/CONFIG_IIO_TRIGGERED_EVENT new file mode 100644 index 000000000000..d9e9ba26a23b --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_IIO_TRIGGERED_EVENT @@ -0,0 +1 @@ +# CONFIG_IIO_TRIGGERED_EVENT is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_ADXRS290 b/redhat/configs/pending-common/generic/CONFIG_ADXRS290 deleted file mode 100644 index b02ec271816d..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_ADXRS290 +++ /dev/null @@ -1,22 +0,0 @@ -# CONFIG_ADXRS290: -# -# Say yes here to build support for Analog Devices ADXRS290 programmable -# digital output gyroscope. -# -# This driver can also be built as a module. If so, the module will be -# called adxrs290. -# -# Symbol: ADXRS290 [=n] -# Type : tristate -# Defined at drivers/iio/gyro/Kconfig:44 -# Prompt: Analog Devices ADXRS290 Dual-Axis MEMS Gyroscope SPI driver -# Depends on: IIO [=m] && SPI [=y] -# Location: -# -> Device Drivers -# -> Industrial I/O support (IIO [=m]) -# -> Digital gyroscope sensors -# Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] -# -# -# -# CONFIG_ADXRS290 is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_AS73211 b/redhat/configs/pending-common/generic/CONFIG_AS73211 deleted file mode 100644 index 74985d5e3d70..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_AS73211 +++ /dev/null @@ -1,25 +0,0 @@ -# CONFIG_AS73211: -# -# If you say yes here you get support for the AMS AS73211 -# JENCOLOR(R) Digital XYZ Sensor. -# -# For triggered measurements, you will need an additional trigger driver -# like IIO_HRTIMER_TRIGGER or IIO_SYSFS_TRIGGER. -# -# This driver can also be built as a module. If so, the module -# will be called as73211. -# -# Symbol: AS73211 [=n] -# Type : tristate -# Defined at drivers/iio/light/Kconfig:89 -# Prompt: AMS AS73211 XYZ color sensor -# Depends on: IIO [=m] && I2C [=y] -# Location: -# -> Device Drivers -# -> Industrial I/O support (IIO [=m]) -# -> Light sensors -# Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] -# -# -# -# CONFIG_AS73211 is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_HDC2010 b/redhat/configs/pending-common/generic/CONFIG_HDC2010 deleted file mode 100644 index 9f4de631e21c..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_HDC2010 +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_HDC2010: -# -# Say yes here to build support for the Texas Instruments -# HDC2010 and HDC2080 relative humidity and temperature sensors. -# -# To compile this driver as a module, choose M here: the module -# will be called hdc2010. -# -# Symbol: HDC2010 [=n] -# Type : tristate -# Defined at drivers/iio/humidity/Kconfig:41 -# Prompt: TI HDC2010 relative humidity and temperature sensor -# Depends on: IIO [=m] && I2C [=y] -# Location: -# -> Device Drivers -# -> Industrial I/O support (IIO [=m]) -# -> Humidity sensors -# -# -# -# CONFIG_HDC2010 is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_IIO_BUFFER_DMA b/redhat/configs/pending-common/generic/CONFIG_IIO_BUFFER_DMA deleted file mode 100644 index 21afc7a2d756..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_IIO_BUFFER_DMA +++ /dev/null @@ -1,23 +0,0 @@ -# CONFIG_IIO_BUFFER_DMA: -# -# Provides the generic IIO DMA buffer infrastructure that can be used by -# drivers for devices with DMA support to implement the IIO buffer. -# -# Should be selected by drivers that want to use the generic DMA buffer -# infrastructure. -# -# Symbol: IIO_BUFFER_DMA [=n] -# Type : tristate -# Defined at drivers/iio/buffer/Kconfig:13 -# Prompt: Industrial I/O DMA buffer infrastructure -# Depends on: IIO [=m] && IIO_BUFFER [=y] -# Location: -# -> Device Drivers -# -> Industrial I/O support (IIO [=m]) -# -> Enable buffer support within IIO (IIO_BUFFER [=y]) -# Selected by [n]: -# - IIO_BUFFER_DMAENGINE [=n] && IIO [=m] && IIO_BUFFER [=y] -# -# -# -# CONFIG_IIO_BUFFER_DMA is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_IIO_BUFFER_DMAENGINE b/redhat/configs/pending-common/generic/CONFIG_IIO_BUFFER_DMAENGINE deleted file mode 100644 index 46d5cb284caf..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_IIO_BUFFER_DMAENGINE +++ /dev/null @@ -1,25 +0,0 @@ -# CONFIG_IIO_BUFFER_DMAENGINE: -# -# Provides a bonding of the generic IIO DMA buffer infrastructure with the -# DMAEngine framework. This can be used by converter drivers with a DMA port -# connected to an external DMA controller which is supported by the -# DMAEngine framework. -# -# Should be selected by drivers that want to use this functionality. -# -# Symbol: IIO_BUFFER_DMAENGINE [=n] -# Type : tristate -# Defined at drivers/iio/buffer/Kconfig:22 -# Prompt: Industrial I/O DMA buffer integration with DMAEngine -# Depends on: IIO [=m] && IIO_BUFFER [=y] -# Location: -# -> Device Drivers -# -> Industrial I/O support (IIO [=m]) -# -> Enable buffer support within IIO (IIO_BUFFER [=y]) -# Selects: IIO_BUFFER_DMA [=n] -# Selected by [n]: -# - ADI_AXI_ADC [=n] && IIO [=m] -# -# -# -# CONFIG_IIO_BUFFER_DMAENGINE is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_IIO_TRIGGERED_EVENT b/redhat/configs/pending-common/generic/CONFIG_IIO_TRIGGERED_EVENT deleted file mode 100644 index d8cf5d290871..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_IIO_TRIGGERED_EVENT +++ /dev/null @@ -1,19 +0,0 @@ -# CONFIG_IIO_TRIGGERED_EVENT: -# -# Provides helper functions for setting up triggered events. -# -# Symbol: IIO_TRIGGERED_EVENT [=n] -# Type : tristate -# Defined at drivers/iio/Kconfig:65 -# Prompt: Enable triggered events support -# Depends on: IIO [=m] -# Location: -# -> Device Drivers -# -> Industrial I/O support (IIO [=m]) -# Selects: IIO_TRIGGER [=y] -# Selected by [n]: -# - HI8435 [=n] && IIO [=m] && SPI [=y] -# -# -# -# CONFIG_IIO_TRIGGERED_EVENT is not set -- GitLab

2 2

[OS-BUILD PATCH] [redhat] New configs in drivers/irqchip
by GitLab Bridge on behalf of jeremycline 11 Jun '21

11 Jun '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_MST_IRQ: Support MStar Interrupt Controller. Symbol: MST_IRQ [=n] Type : bool Defined at drivers/irqchip/Kconfig:584 Prompt: MStar Interrupt Controller Location: -> Device Drivers -> IRQ chip support Selects: IRQ_DOMAIN [=y] && IRQ_DOMAIN_HIERARCHY [=y] --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/common/generic/CONFIG_MST_IRQ | 1 + .../pending-common/generic/CONFIG_MST_IRQ | 16 ---------------- 2 files changed, 1 insertion(+), 16 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_MST_IRQ delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MST_IRQ diff --git a/redhat/configs/common/generic/CONFIG_MST_IRQ b/redhat/configs/common/generic/CONFIG_MST_IRQ new file mode 100644 index 000000000000..80d5aeca4332 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_MST_IRQ @@ -0,0 +1 @@ +# CONFIG_MST_IRQ is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_MST_IRQ b/redhat/configs/pending-common/generic/CONFIG_MST_IRQ deleted file mode 100644 index a26929e93f0e..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_MST_IRQ +++ /dev/null @@ -1,16 +0,0 @@ -# CONFIG_MST_IRQ: -# -# Support MStar Interrupt Controller. -# -# Symbol: MST_IRQ [=n] -# Type : bool -# Defined at drivers/irqchip/Kconfig:584 -# Prompt: MStar Interrupt Controller -# Location: -# -> Device Drivers -# -> IRQ chip support -# Selects: IRQ_DOMAIN [=y] && IRQ_DOMAIN_HIERARCHY [=y] -# -# -# -# CONFIG_MST_IRQ is not set -- GitLab

2 1

[OS-BUILD PATCH] [redhat] New configs in drivers/net/pcs
by GitLab Bridge on behalf of jeremycline 10 Jun '21

10 Jun '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_PCS_XPCS: This module provides helper functions for Synopsys DesignWare XPCS controllers. Symbol: PCS_XPCS [=n] Type : tristate Defined at drivers/net/pcs/Kconfig:8 Prompt: Synopsys DesignWare XPCS controller Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y] Location: -> Device Drivers -> Network device support (NETDEVICES [=y]) -> PCS device drivers Selects: MDIO_BUS [=y] Selected by [n]: - STMMAC_ETH [=n] && NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_STMICRO [=n] && HAS_IOMEM [=y] && HAS_DMA [=y] --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/common/generic/CONFIG_PCS_XPCS | 1 + .../pending-common/generic/CONFIG_PCS_XPCS | 21 ------------------- 2 files changed, 1 insertion(+), 21 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_PCS_XPCS delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PCS_XPCS diff --git a/redhat/configs/common/generic/CONFIG_PCS_XPCS b/redhat/configs/common/generic/CONFIG_PCS_XPCS new file mode 100644 index 000000000000..ca3dfae8d1b1 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_PCS_XPCS @@ -0,0 +1 @@ +# CONFIG_PCS_XPCS is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_PCS_XPCS b/redhat/configs/pending-common/generic/CONFIG_PCS_XPCS deleted file mode 100644 index fad45873ffb5..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_PCS_XPCS +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_PCS_XPCS: -# -# This module provides helper functions for Synopsys DesignWare XPCS -# controllers. -# -# Symbol: PCS_XPCS [=n] -# Type : tristate -# Defined at drivers/net/pcs/Kconfig:8 -# Prompt: Synopsys DesignWare XPCS controller -# Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y] -# Location: -# -> Device Drivers -# -> Network device support (NETDEVICES [=y]) -# -> PCS device drivers -# Selects: MDIO_BUS [=y] -# Selected by [n]: -# - STMMAC_ETH [=n] && NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_STMICRO [=n] && HAS_IOMEM [=y] && HAS_DMA [=y] -# -# -# -# CONFIG_PCS_XPCS is not set -- GitLab

2 1

[OS-BUILD PATCH] [redhat] New configs in fs/cifs
by GitLab Bridge on behalf of redhat-patchlab 07 Jun '21

07 Jun '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_CIFS_SWN_UPCALL: The Service Witness Protocol (SWN) is used to get notifications from a highly available server of resource state changes. This feature enables an upcall mechanism for CIFS which contacts a userspace daemon to establish the DCE/RPC connection to retrieve the cluster available interfaces and resource change notifications. If unsure, say Y. Symbol: CIFS_SWN_UPCALL [=n] Type : bool Defined at fs/cifs/Kconfig:193 Prompt: SWN feature support Depends on: NETWORK_FILESYSTEMS [=y] && CIFS [=m] Location: -> File systems -> Network File Systems (NETWORK_FILESYSTEMS [=y]) -> SMB3 and CIFS support (advanced network filesystem) (CIFS [=m]) --- Cc: kernel-patches(a)redhat.com Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_CIFS_SWN_UPCALL | 1 + .../generic/CONFIG_CIFS_SWN_UPCALL | 22 ------------------- 2 files changed, 1 insertion(+), 22 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_CIFS_SWN_UPCALL delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CIFS_SWN_UPCALL diff --git a/redhat/configs/common/generic/CONFIG_CIFS_SWN_UPCALL b/redhat/configs/common/generic/CONFIG_CIFS_SWN_UPCALL new file mode 100644 index 000000000000..895af9460510 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_CIFS_SWN_UPCALL @@ -0,0 +1 @@ +# CONFIG_CIFS_SWN_UPCALL is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_CIFS_SWN_UPCALL b/redhat/configs/pending-common/generic/CONFIG_CIFS_SWN_UPCALL deleted file mode 100644 index 4b677e712849..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_CIFS_SWN_UPCALL +++ /dev/null @@ -1,22 +0,0 @@ -# CONFIG_CIFS_SWN_UPCALL: -# -# The Service Witness Protocol (SWN) is used to get notifications -# from a highly available server of resource state changes. This -# feature enables an upcall mechanism for CIFS which contacts a -# userspace daemon to establish the DCE/RPC connection to retrieve -# the cluster available interfaces and resource change notifications. -# If unsure, say Y. -# -# Symbol: CIFS_SWN_UPCALL [=n] -# Type : bool -# Defined at fs/cifs/Kconfig:193 -# Prompt: SWN feature support -# Depends on: NETWORK_FILESYSTEMS [=y] && CIFS [=m] -# Location: -# -> File systems -# -> Network File Systems (NETWORK_FILESYSTEMS [=y]) -# -> SMB3 and CIFS support (advanced network filesystem) (CIFS [=m]) -# -# -# -# CONFIG_CIFS_SWN_UPCALL is not set -- GitLab

5 4

[OS-BUILD PATCH] [redhat] Add GIT macro to Makefile and Makefile.common:
by GitLab Bridge on behalf of bcrocker 21 May '21

21 May '21

From: Ben Crocker <bcrocker(a)redhat.com> GIT ?= git and replace literal occurrences of 'git' with $(GIT). This change enables us to override 'git' with, e.g., some arbitrary shell script that prints additional information and/or does additional processing before and/or after (or even instead of) invoking /usr/bin/git. Signed-off-by: Ben Crocker <bcrocker(a)redhat.com> --- redhat/Makefile | 29 +++++++++++++++-------------- redhat/Makefile.common | 16 ++++++++-------- 2 files changed, 23 insertions(+), 22 deletions(-) diff --git a/redhat/Makefile b/redhat/Makefile index 27d2cd94e78f..ee3702434e05 100644 --- a/redhat/Makefile +++ b/redhat/Makefile @@ -1,3 +1,4 @@ +GIT ?= git include Makefile.common include Makefile.rhpkg @@ -32,8 +33,8 @@ endif BUILD_TARGET ?= --scratch $(BUILD_SCRATCH_TARGET) FLAVOR = -RHGITURL?=$(shell git config rhg.url || git config remote.origin.url) -RHGITCOMMIT?=$(shell git log -1 --pretty=format:%H) +RHGITURL?=$(shell $(GIT) config rhg.url || $(GIT) config remote.origin.url) +RHGITCOMMIT?=$(shell $(GIT) log -1 --pretty=format:%H) # this section is needed in order to make O= to work _OUTPUT := .. @@ -199,7 +200,7 @@ $(KABIDW_TARBALL): dist-git-version-check: @# genspec.sh uses pathspec magic that wasn't introduced until version 2.13 @IFS=" ."; \ - set -- $$(git --version); \ + set -- $$($(GIT) --version); \ IFS=; \ if [ "$$3" -lt 2 -o $ "$$3" -eq 2 -a "$$4" -lt 13 $ ]; then \ echo "ERROR: You need git version 2.13 or newer to run some setup commands"; \ @@ -219,7 +220,7 @@ setup-source: dist-git-version-check dist-clean-sources sources-rh: $(TARBALL) @cp -l $(TARBALL) $(SOURCES)/ || cp $(TARBALL) $(SOURCES)/ @touch $(TESTPATCH) - @git diff --no-renames HEAD > $(TESTPATCH).tmp + @$(GIT) diff --no-renames HEAD > $(TESTPATCH).tmp @# 1) filterdiff will return crap from the patches it just filtered, @# that's why egrep is needed so if there're changes under redhat/ @# but not everywhere else, it will be empty just like @@ -265,7 +266,7 @@ sources-rh: $(TARBALL) dist-sources: setup-source dist-configs-check dist-kabi dist-kabi-dup sources-rh dist-test-patch: - @git diff --no-renames HEAD > $(TESTPATCH); + @$(GIT) diff --no-renames HEAD > $(TESTPATCH); @($(FILTERDIFF) $(TESTPATCH) | egrep -v "^index|^diff" >$(TESTPATCH).tmp; true) @mv $(TESTPATCH).tmp $(TESTPATCH); @@ -300,34 +301,34 @@ dist-release-finish: setup-source @cp $(SOURCES)/$(CHANGELOG) $(REDHAT)/$(CHANGELOG) @echo $(MARKER) > $(REDHAT)/marker @# if neither changelog nor marker was updated, skip bumping a release - git diff-index --quiet HEAD && (echo "Nothing changed, skipping updates"; exit 0) || true + $(GIT) diff-index --quiet HEAD && (echo "Nothing changed, skipping updates"; exit 0) || true $(REDHAT)/scripts/new_release.sh $(REDHAT) $(__YSTREAM) $(__ZSTREAM); \ - git add $(REDHAT)/$(CHANGELOG); \ - git add $(REDHAT)/marker; \ - git commit -s ../Makefile.rhelver $(REDHAT)/marker $(REDHAT)/$(CHANGELOG) $(PACKAGE_NAME).spec.template -m "[redhat] $(PACKAGE_NAME)-$(STAMP_VERSION)-$(PREBUILD)$(BUILD)$(BUILDID)"; \ + $(GIT) add $(REDHAT)/$(CHANGELOG); \ + $(GIT) add $(REDHAT)/marker; \ + $(GIT) commit -s ../Makefile.rhelver $(REDHAT)/marker $(REDHAT)/$(CHANGELOG) $(PACKAGE_NAME).spec.template -m "[redhat] $(PACKAGE_NAME)-$(STAMP_VERSION)-$(PREBUILD)$(BUILD)$(BUILDID)"; \ dist-release: dist-clean-sources @$(MAKE) dist-release-finish dist-release-tag: - @git tag -a -m "$(PACKAGE_NAME)-$(STAMP_VERSION)-$(PKGRELEASE)" $(PACKAGE_NAME)-$(STAMP_VERSION)-$(PKGRELEASE) + @$(GIT) tag -a -m "$(PACKAGE_NAME)-$(STAMP_VERSION)-$(PKGRELEASE)" $(PACKAGE_NAME)-$(STAMP_VERSION)-$(PKGRELEASE) git-tree-check: - @if test -n "$(DIST_PUSH)" && test -z "$(shell git remote get-url gitlab 2>/dev/null)"; then \ + @if test -n "$(DIST_PUSH)" && test -z "$(shell $(GIT) remote get-url gitlab 2>/dev/null)"; then \ echo -e "Please run 'git remote add gitlab <url>' to enable git-push.\n"; \ exit 1; \ fi - @git diff-index --quiet HEAD || \ + @$(GIT) diff-index --quiet HEAD || \ { echo -e "Dirty tree, please clean before merging.\n"; exit 1; } DIST_BRANCH ?= "os-build" dist-merge-upstream: git-tree-check - @if test "$(shell git branch --show-current)" != "$(DIST_BRANCH)"; then \ + @if test "$(shell $(GIT) branch --show-current)" != "$(DIST_BRANCH)"; then \ echo -e "Please checkout $(DIST_BRANCH) branch before merging.\n"; \ exit 1; \ fi; @# If TAG is empty, script defaults to master:HEAD - git checkout $(DIST_BRANCH) + $(GIT) checkout $(DIST_BRANCH) @$(REDHAT)/scripts/ci/ark-update-configs.sh $(TAG) dist-merge-upstream-push: export DIST_PUSH="1" diff --git a/redhat/Makefile.common b/redhat/Makefile.common index b335f3c77c7d..80c3b8dfccd4 100644 --- a/redhat/Makefile.common +++ b/redhat/Makefile.common @@ -1,4 +1,4 @@ -TOPDIR:=$(shell git rev-parse --show-toplevel) +TOPDIR:=$(shell $(GIT) rev-parse --show-toplevel) REDHAT:=$(TOPDIR)/redhat include $(TOPDIR)/Makefile.rhelver @@ -6,11 +6,11 @@ RPMBUILD := $(shell if [ -x "/usr/bin/rpmbuild" ]; then echo rpmbuild; \ else echo rpm; fi) MACH := $(shell uname -m) -RPMKVERSION:=$(shell git show HEAD:Makefile | sed -ne '/^VERSION\ =\ /{s///;p;q}') -RPMKPATCHLEVEL:=$(shell git show HEAD:Makefile | sed -ne '/^PATCHLEVEL\ =\ /{s///;p;q}') -RPMKSUBLEVEL:=$(shell git show HEAD:Makefile | sed -ne '/^SUBLEVEL\ =\ /{s///;p;q}') -RPMKEXTRAVERSION:=$(shell git show HEAD:Makefile | sed -ne '/^EXTRAVERSION\ =\ /{s///;p;q}') -GITID:= $(shell git log --max-count=1 --pretty=format:%H) +RPMKVERSION:=$(shell $(GIT) show HEAD:Makefile | sed -ne '/^VERSION\ =\ /{s///;p;q}') +RPMKPATCHLEVEL:=$(shell $(GIT) show HEAD:Makefile | sed -ne '/^PATCHLEVEL\ =\ /{s///;p;q}') +RPMKSUBLEVEL:=$(shell $(GIT) show HEAD:Makefile | sed -ne '/^SUBLEVEL\ =\ /{s///;p;q}') +RPMKEXTRAVERSION:=$(shell $(GIT) show HEAD:Makefile | sed -ne '/^EXTRAVERSION\ =\ /{s///;p;q}') +GITID:= $(shell $(GIT) log --max-count=1 --pretty=format:%H) # marker is git tag which we base off of for exporting patches # Make sure marker uses RPMKPATCHLEVEL and RPMKEXTRAVERSION from the kernel # makefile as opposed to any adjusted version for snapshotting. @@ -42,8 +42,8 @@ else endif ifeq ($(VERSION_ON_UPSTREAM),1) # master is expected to track mainline. - MERGE_BASE:=$(shell git merge-base HEAD master) - _TAG:=$(shell git describe $(MERGE_BASE)) + MERGE_BASE:=$(shell $(GIT) merge-base HEAD master) + _TAG:=$(shell $(GIT) describe $(MERGE_BASE)) # a snapshot off of a tagged git is of the form [tag]-[cnt]-g[hash] SNAPSHOT:=$(shell echo $(_TAG) | grep -c '\-g') else -- GitLab

17 241

[OS-BUILD PATCH] Fix branch creation for releases based on tags
by GitLab Bridge on behalf of jeremycline 10 May '21

10 May '21

From: Jeremy Cline <jcline(a)redhat.com> The release scripts are supposed create a set of branches if the release is based of a tag rather than a snapshot. davidlt noted on IRC that branches were missing for recent tags, namely rc3 and rc4. The reason is that the check for a signed tag expects $UPSTREAM_REF to be the tag. Resolve $UPSTREAM_REF to a tag (if it exists) prior to verifying the tag. Signed-off-by: Jeremy Cline <jcline(a)redhat.com> --- redhat/scripts/ci/ark-create-release.sh | 2 +- redhat/scripts/ci/ark-rebase-patches.sh | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/redhat/scripts/ci/ark-create-release.sh b/redhat/scripts/ci/ark-create-release.sh index fd57e533ddb4..83b102ceb54f 100755 --- a/redhat/scripts/ci/ark-create-release.sh +++ b/redhat/scripts/ci/ark-create-release.sh @@ -37,7 +37,7 @@ git checkout os-build git checkout os-build ./redhat/scripts/ci/ark-update-configs.sh "$UPSTREAM_REF" "$PROJECT_ID" -if git tag -v "$UPSTREAM_REF" > /dev/null 2>&1; then +if git tag -v "$(git describe --exact-match "$UPSTREAM_REF")"; then git checkout -b ark/"$UPSTREAM_REF" ark/patches/"$UPSTREAM_REF" RELEASE_BRANCHES=" ark/$UPSTREAM_REF ark/patches/$UPSTREAM_REF" else diff --git a/redhat/scripts/ci/ark-rebase-patches.sh b/redhat/scripts/ci/ark-rebase-patches.sh index 2ac22bcba3bd..4a02176bde88 100755 --- a/redhat/scripts/ci/ark-rebase-patches.sh +++ b/redhat/scripts/ci/ark-rebase-patches.sh @@ -102,7 +102,7 @@ else exit 2 fi -if git tag -v "$UPSTREAM_REF" > /dev/null 2>&1; then +if git tag -v "$(git describe --exact-match "$UPSTREAM_REF")"; then printf "Creating branch \"ark/patches/%s\"\n" "$UPSTREAM_REF" git branch ark/patches/"$UPSTREAM_REF" printf "Don't forget to run 'git push <remote> ark/patches/%s'\n" "$UPSTREAM_REF" -- 2.26.2

2 1

[OS-BUILD PATCH] [redhat] New configs in drivers/bus
by GitLab Bridge on behalf of jeremycline 06 May '21

06 May '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_VEXPRESS_CONFIG: Platform configuration infrastructure for the ARM Ltd. Versatile Express. Symbol: VEXPRESS_CONFIG [=y] Type : tristate Defined at drivers/bus/Kconfig:224 Prompt: Versatile Express configuration bus Depends on: (ARM || ARM64 [=y]) && OF [=y] Location: -> Device Drivers -> Bus devices Selects: REGMAP [=y] --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_VEXPRESS_CONFIG | 1 + .../generic/CONFIG_VEXPRESS_CONFIG | 18 ------------------ 2 files changed, 1 insertion(+), 18 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_VEXPRESS_CONFIG delete mode 100644 redhat/configs/pending-common/generic/CONFIG_VEXPRESS_CONFIG diff --git a/redhat/configs/common/generic/CONFIG_VEXPRESS_CONFIG b/redhat/configs/common/generic/CONFIG_VEXPRESS_CONFIG new file mode 100644 index 000000000000..389660309f56 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_VEXPRESS_CONFIG @@ -0,0 +1 @@ +CONFIG_VEXPRESS_CONFIG=y diff --git a/redhat/configs/pending-common/generic/CONFIG_VEXPRESS_CONFIG b/redhat/configs/pending-common/generic/CONFIG_VEXPRESS_CONFIG deleted file mode 100644 index a2c1cb307e90..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_VEXPRESS_CONFIG +++ /dev/null @@ -1,18 +0,0 @@ -# CONFIG_VEXPRESS_CONFIG: -# -# Platform configuration infrastructure for the ARM Ltd. -# Versatile Express. -# -# Symbol: VEXPRESS_CONFIG [=y] -# Type : tristate -# Defined at drivers/bus/Kconfig:224 -# Prompt: Versatile Express configuration bus -# Depends on: (ARM || ARM64 [=y]) && OF [=y] -# Location: -# -> Device Drivers -# -> Bus devices -# Selects: REGMAP [=y] -# -# -# -CONFIG_VEXPRESS_CONFIG=y -- 2.26.2

6 7

[OS-BUILD PATCH] [redhat] New configs in drivers/net/dsa
by CKI Gitlab (via Email Bridge) 04 May '21

04 May '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/net/dsa Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_NET_DSA_MV88E6XXX_PTP: Say Y to enable PTP hardware timestamping on Marvell 88E6xxx switch chips that support it. Symbol: NET_DSA_MV88E6XXX_PTP [=n] Type : bool Defined at drivers/net/dsa/mv88e6xxx/Kconfig:12 Prompt: PTP support for Marvell 88E6xxx Depends on: NETDEVICES [=y] && HAVE_NET_DSA [=y] && PTP_1588_CLOCK [=y] Location: -> Device Drivers -> Network device support (NETDEVICES [=y]) -> Distributed Switch Architecture drivers --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_NET_DSA_MV88E6XXX_PTP b/redhat/configs/common/generic/CONFIG_NET_DSA_MV88E6XXX_PTP --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_NET_DSA_MV88E6XXX_PTP @@ -0,0 +1 @@ +# CONFIG_NET_DSA_MV88E6XXX_PTP is not set diff a/redhat/configs/pending-common/generic/CONFIG_NET_DSA_MV88E6XXX_PTP b/redhat/configs/pending-common/generic/CONFIG_NET_DSA_MV88E6XXX_PTP --- a/redhat/configs/pending-common/generic/CONFIG_NET_DSA_MV88E6XXX_PTP +++ /dev/null @@ -1,18 +0,0 @@ -# CONFIG_NET_DSA_MV88E6XXX_PTP: -# -# Say Y to enable PTP hardware timestamping on Marvell 88E6xxx switch -# chips that support it. -# -# Symbol: NET_DSA_MV88E6XXX_PTP [=n] -# Type : bool -# Defined at drivers/net/dsa/mv88e6xxx/Kconfig:12 -# Prompt: PTP support for Marvell 88E6xxx -# Depends on: NETDEVICES [=y] && HAVE_NET_DSA [=y] && PTP_1588_CLOCK [=y] -# Location: -# -> Device Drivers -# -> Network device support (NETDEVICES [=y]) -# -> Distributed Switch Architecture drivers -# -# -# -# CONFIG_NET_DSA_MV88E6XXX_PTP is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/907

3 2

[OS-BUILD PATCH] [redhat] New configs in fs/nfs
by GitLab Bridge on behalf of redhat-patchlab 03 May '21

03 May '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_NFS_V4_2_READ_PLUS: This is intended for developers only. The READ_PLUS operation has been shown to have issues under specific conditions and should not be used in production. Symbol: NFS_V4_2_READ_PLUS [=n] Type : bool Defined at fs/nfs/Kconfig:209 Prompt: NFS: Enable support for the NFSv4.2 READ_PLUS operation Depends on: NETWORK_FILESYSTEMS [=y] && NFS_V4_2 [=y] Location: -> File systems -> Network File Systems (NETWORK_FILESYSTEMS [=y]) --- Cc: kernel-patches(a)redhat.com Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_NFS_V4_2_READ_PLUS | 1 + .../generic/CONFIG_NFS_V4_2_READ_PLUS | 18 ------------------ 2 files changed, 1 insertion(+), 18 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_NFS_V4_2_READ_PLUS delete mode 100644 redhat/configs/pending-common/generic/CONFIG_NFS_V4_2_READ_PLUS diff --git a/redhat/configs/common/generic/CONFIG_NFS_V4_2_READ_PLUS b/redhat/configs/common/generic/CONFIG_NFS_V4_2_READ_PLUS new file mode 100644 index 000000000000..4d62001f1f91 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_NFS_V4_2_READ_PLUS @@ -0,0 +1 @@ +# CONFIG_NFS_V4_2_READ_PLUS is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_NFS_V4_2_READ_PLUS b/redhat/configs/pending-common/generic/CONFIG_NFS_V4_2_READ_PLUS deleted file mode 100644 index 5a90e4f7db16..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_NFS_V4_2_READ_PLUS +++ /dev/null @@ -1,18 +0,0 @@ -# CONFIG_NFS_V4_2_READ_PLUS: -# -# This is intended for developers only. The READ_PLUS operation has -# been shown to have issues under specific conditions and should not -# be used in production. -# -# Symbol: NFS_V4_2_READ_PLUS [=n] -# Type : bool -# Defined at fs/nfs/Kconfig:209 -# Prompt: NFS: Enable support for the NFSv4.2 READ_PLUS operation -# Depends on: NETWORK_FILESYSTEMS [=y] && NFS_V4_2 [=y] -# Location: -# -> File systems -# -> Network File Systems (NETWORK_FILESYSTEMS [=y]) -# -# -# -# CONFIG_NFS_V4_2_READ_PLUS is not set -- GitLab

6 11

[OS-BUILD PATCH] [redhat] New configs in drivers/rtc
by GitLab Bridge on behalf of redhat-patchlab 03 May '21

03 May '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_RTC_DRV_GOLDFISH: Say yes to enable RTC driver for the Goldfish based virtual platform. Goldfish is a code name for the virtual platform developed by Google for Android emulation. Symbol: RTC_DRV_GOLDFISH [=n] Type : tristate Defined at drivers/rtc/Kconfig:1943 Prompt: Goldfish Real Time Clock Depends on: RTC_CLASS [=y] && OF [=y] && HAS_IOMEM [=y] Location: -> Device Drivers -> Real Time Clock (RTC_CLASS [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_RTC_DRV_GOLDFISH | 1 + .../generic/CONFIG_RTC_DRV_GOLDFISH | 19 ------------------- 2 files changed, 1 insertion(+), 19 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_RTC_DRV_GOLDFISH delete mode 100644 redhat/configs/pending-common/generic/CONFIG_RTC_DRV_GOLDFISH diff --git a/redhat/configs/common/generic/CONFIG_RTC_DRV_GOLDFISH b/redhat/configs/common/generic/CONFIG_RTC_DRV_GOLDFISH new file mode 100644 index 000000000000..4b7e561b61de --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_RTC_DRV_GOLDFISH @@ -0,0 +1 @@ +# CONFIG_RTC_DRV_GOLDFISH is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_RTC_DRV_GOLDFISH b/redhat/configs/pending-common/generic/CONFIG_RTC_DRV_GOLDFISH deleted file mode 100644 index cfb8193b9bb0..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_RTC_DRV_GOLDFISH +++ /dev/null @@ -1,19 +0,0 @@ -# CONFIG_RTC_DRV_GOLDFISH: -# -# Say yes to enable RTC driver for the Goldfish based virtual platform. -# -# Goldfish is a code name for the virtual platform developed by Google -# for Android emulation. -# -# Symbol: RTC_DRV_GOLDFISH [=n] -# Type : tristate -# Defined at drivers/rtc/Kconfig:1943 -# Prompt: Goldfish Real Time Clock -# Depends on: RTC_CLASS [=y] && OF [=y] && HAS_IOMEM [=y] -# Location: -# -> Device Drivers -# -> Real Time Clock (RTC_CLASS [=y]) -# -# -# -# CONFIG_RTC_DRV_GOLDFISH is not set -- GitLab

3 2

Erase i686 from the kernel package's repository?
by Paul Bolle 22 Apr '21

22 Apr '21

Hi Justin, Fedora 31's release is imminent. This means that some time ago Fedora passed the point where (F31 and later) i686 releases were still possible, doesn't it? If so, could we please clean the kernel package's repository of all the things that are only relevant for i686? Because that would make my plans for the config generation [1] just a bit easier. Thanks, Paul Bolle [1] See https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.or…

4 16

[OS-BUILD PATCH] [redhat] New configs in sound/soc
by CKI Gitlab (via Email Bridge) 20 Apr '21

20 Apr '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in sound/soc Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK: This adds support for SoundWire with Sound Open Firmware for Intel(R) platforms. Say Y if you want to enable SoundWire links with SOF. If unsure select "N". Symbol: SND_SOC_SOF_INTEL_SOUNDWIRE_LINK [=n] Type : bool Defined at sound/soc/sof/intel/Kconfig:356 Prompt: SOF support for SoundWire Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_SOF_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_PCI [=m] && ACPI [=y] Location: -> Device Drivers -> Sound card support (SOUND [=m]) -> Advanced Linux Sound Architecture (SND [=m]) -> ALSA for SoC audio support (SND_SOC [=m]) -> Sound Open Firmware Support (SND_SOC_SOF_TOPLEVEL [=y]) -> SOF support for Intel audio DSPs (SND_SOC_SOF_INTEL_TOPLEVEL [=y]) --- Cc: Jaroslav Kysela <jkysela(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK b/redhat/configs/common/generic/CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK @@ -0,0 +1 @@ +# CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK is not set diff a/redhat/configs/pending-common/generic/CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK b/redhat/configs/pending-common/generic/CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK --- a/redhat/configs/pending-common/generic/CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK +++ /dev/null @@ -1,23 +0,0 @@ -# CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK: -# -# This adds support for SoundWire with Sound Open Firmware -# for Intel(R) platforms. -# Say Y if you want to enable SoundWire links with SOF. -# If unsure select "N". -# -# Symbol: SND_SOC_SOF_INTEL_SOUNDWIRE_LINK [=n] -# Type : bool -# Defined at sound/soc/sof/intel/Kconfig:356 -# Prompt: SOF support for SoundWire -# Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_SOF_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_PCI [=m] && ACPI [=y] -# Location: -# -> Device Drivers -# -> Sound card support (SOUND [=m]) -# -> Advanced Linux Sound Architecture (SND [=m]) -# -> ALSA for SoC audio support (SND_SOC [=m]) -# -> Sound Open Firmware Support (SND_SOC_SOF_TOPLEVEL [=y]) -# -> SOF support for Intel audio DSPs (SND_SOC_SOF_INTEL_TOPLEVEL [=y]) -# -# -# -# CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/875

3 3

[OS-BUILD PATCH] [redhat] New configs in arch/s390
by CKI Gitlab (via Email Bridge) 20 Apr '21

20 Apr '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in arch/s390 Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_DEBUG_ENTRY: This option enables sanity checks in s390 low-level entry code. Some of these sanity checks may slow down kernel entries and exits or otherwise impact performance. If unsure, say N. Symbol: DEBUG_ENTRY [=n] Type : bool Defined at arch/s390/Kconfig.debug:9 Prompt: Debug low-level entry code Depends on: DEBUG_KERNEL [=y] Location: -> Kernel hacking -> s390 Debugging --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_DEBUG_ENTRY b/redhat/configs/common/generic/CONFIG_DEBUG_ENTRY --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_DEBUG_ENTRY @@ -0,0 +1 @@ +# CONFIG_DEBUG_ENTRY is not set diff a/redhat/configs/pending-common/generic/CONFIG_DEBUG_ENTRY b/redhat/configs/pending-common/generic/CONFIG_DEBUG_ENTRY --- a/redhat/configs/pending-common/generic/CONFIG_DEBUG_ENTRY +++ /dev/null @@ -1,20 +0,0 @@ -# CONFIG_DEBUG_ENTRY: -# -# This option enables sanity checks in s390 low-level entry code. -# Some of these sanity checks may slow down kernel entries and -# exits or otherwise impact performance. -# -# If unsure, say N. -# -# Symbol: DEBUG_ENTRY [=n] -# Type : bool -# Defined at arch/s390/Kconfig.debug:9 -# Prompt: Debug low-level entry code -# Depends on: DEBUG_KERNEL [=y] -# Location: -# -> Kernel hacking -# -> s390 Debugging -# -# -# -# CONFIG_DEBUG_ENTRY is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/900

3 6

[OS-BUILD PATCH] [redhat] New configs in drivers/gpu
by GitLab Bridge on behalf of jeremycline 16 Apr '21

16 Apr '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_DRM_AMD_DC_DCN3_0: Choose this option if you want to have sienna_cichlid support for display engine Symbol: DRM_AMD_DC_DCN3_0 [=n] Type : bool Defined at drivers/gpu/drm/amd/display/Kconfig:20 Prompt: DCN 3.0 family Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_AMDGPU [=m] && DRM_AMD_DC [=y] && X86 [=y] && DRM_AMD_DC_DCN [=y] Location: -> Device Drivers -> Graphics support -> AMD GPU (DRM_AMDGPU [=m]) -> Display Engine Configuration --- CONFIG_NOUVEAU_DEBUG_PUSH: Say Y here if you want to enable verbose push buffer debug output and sanity checks. Symbol: NOUVEAU_DEBUG_PUSH [=n] Type : bool Defined at drivers/gpu/drm/nouveau/Kconfig:79 Prompt: Enable additional push buffer debugging Depends on: HAS_IOMEM [=y] && DRM_NOUVEAU [=m] Location: -> Device Drivers -> Graphics support -> Nouveau (NVIDIA) cards (DRM_NOUVEAU [=m]) --- Cc: David Airlie <airlied(a)redhat.com> Cc: Adam Jackson <ajax(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_DRM_AMD_DC_DCN3_0 | 1 + .../common/generic/CONFIG_NOUVEAU_DEBUG_PUSH | 1 + .../generic/CONFIG_DRM_AMD_DC_DCN3_0 | 19 ------------------- .../generic/CONFIG_NOUVEAU_DEBUG_PUSH | 18 ------------------ 4 files changed, 2 insertions(+), 37 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_DRM_AMD_DC_DCN3_0 create mode 100644 redhat/configs/common/generic/CONFIG_NOUVEAU_DEBUG_PUSH delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DRM_AMD_DC_DCN3_0 delete mode 100644 redhat/configs/pending-common/generic/CONFIG_NOUVEAU_DEBUG_PUSH diff --git a/redhat/configs/common/generic/CONFIG_DRM_AMD_DC_DCN3_0 b/redhat/configs/common/generic/CONFIG_DRM_AMD_DC_DCN3_0 new file mode 100644 index 000000000000..708bd22e809e --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_DRM_AMD_DC_DCN3_0 @@ -0,0 +1 @@ +# CONFIG_DRM_AMD_DC_DCN3_0 is not set diff --git a/redhat/configs/common/generic/CONFIG_NOUVEAU_DEBUG_PUSH b/redhat/configs/common/generic/CONFIG_NOUVEAU_DEBUG_PUSH new file mode 100644 index 000000000000..5614c2c49809 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_NOUVEAU_DEBUG_PUSH @@ -0,0 +1 @@ +# CONFIG_NOUVEAU_DEBUG_PUSH is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_DRM_AMD_DC_DCN3_0 b/redhat/configs/pending-common/generic/CONFIG_DRM_AMD_DC_DCN3_0 deleted file mode 100644 index f6a3c764772e..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_DRM_AMD_DC_DCN3_0 +++ /dev/null @@ -1,19 +0,0 @@ -# CONFIG_DRM_AMD_DC_DCN3_0: -# -# Choose this option if you want to have -# sienna_cichlid support for display engine -# -# Symbol: DRM_AMD_DC_DCN3_0 [=n] -# Type : bool -# Defined at drivers/gpu/drm/amd/display/Kconfig:20 -# Prompt: DCN 3.0 family -# Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_AMDGPU [=m] && DRM_AMD_DC [=y] && X86 [=y] && DRM_AMD_DC_DCN [=y] -# Location: -# -> Device Drivers -# -> Graphics support -# -> AMD GPU (DRM_AMDGPU [=m]) -# -> Display Engine Configuration -# -# -# -# CONFIG_DRM_AMD_DC_DCN3_0 is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_NOUVEAU_DEBUG_PUSH b/redhat/configs/pending-common/generic/CONFIG_NOUVEAU_DEBUG_PUSH deleted file mode 100644 index c28eaf703375..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_NOUVEAU_DEBUG_PUSH +++ /dev/null @@ -1,18 +0,0 @@ -# CONFIG_NOUVEAU_DEBUG_PUSH: -# -# Say Y here if you want to enable verbose push buffer debug output -# and sanity checks. -# -# Symbol: NOUVEAU_DEBUG_PUSH [=n] -# Type : bool -# Defined at drivers/gpu/drm/nouveau/Kconfig:79 -# Prompt: Enable additional push buffer debugging -# Depends on: HAS_IOMEM [=y] && DRM_NOUVEAU [=m] -# Location: -# -> Device Drivers -# -> Graphics support -# -> Nouveau (NVIDIA) cards (DRM_NOUVEAU [=m]) -# -# -# -# CONFIG_NOUVEAU_DEBUG_PUSH is not set -- GitLab

7 8

[OS-BUILD PATCH] [redhat] New configs in drivers/vdpa
by GitLab Bridge on behalf of redhat-patchlab 16 Apr '21

16 Apr '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. --- Cc: "Michael S. Tsirkin" <mst(a)redhat.com> Cc: Jason Wang <jasowang(a)redhat.com> Cc: rhvirt-patches(a)redhat.com Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/common/generic/CONFIG_VDPA_SIM_NET | 0 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_VDPA_SIM_NET diff --git a/redhat/configs/common/generic/CONFIG_VDPA_SIM_NET b/redhat/configs/common/generic/CONFIG_VDPA_SIM_NET new file mode 100644 index 000000000000..e69de29bb2d1 -- GitLab

6 8

[OS-BUILD PATCH] [redhat] New configs in drivers/power
by GitLab Bridge on behalf of jeremycline 14 Apr '21

14 Apr '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_POWER_RESET_VEXPRESS: Power off and reset support for the ARM Ltd. Versatile Express boards. Symbol: POWER_RESET_VEXPRESS [=n] Type : bool Defined at drivers/power/reset/Kconfig:184 Prompt: ARM Versatile Express power-off and reset driver Depends on: POWER_RESET [=y] && (ARM || ARM64 [=y]) && VEXPRESS_CONFIG [=y]=y Location: -> Device Drivers -> Board level reset or power off (POWER_RESET [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_POWER_RESET_VEXPRESS | 1 + .../generic/CONFIG_POWER_RESET_VEXPRESS | 17 ----------------- 2 files changed, 1 insertion(+), 17 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_POWER_RESET_VEXPRESS delete mode 100644 redhat/configs/pending-common/generic/CONFIG_POWER_RESET_VEXPRESS diff --git a/redhat/configs/common/generic/CONFIG_POWER_RESET_VEXPRESS b/redhat/configs/common/generic/CONFIG_POWER_RESET_VEXPRESS new file mode 100644 index 000000000000..6b285d5c913a --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_POWER_RESET_VEXPRESS @@ -0,0 +1 @@ +# CONFIG_POWER_RESET_VEXPRESS is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_POWER_RESET_VEXPRESS b/redhat/configs/pending-common/generic/CONFIG_POWER_RESET_VEXPRESS deleted file mode 100644 index 80e0a957fff8..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_POWER_RESET_VEXPRESS +++ /dev/null @@ -1,17 +0,0 @@ -# CONFIG_POWER_RESET_VEXPRESS: -# -# Power off and reset support for the ARM Ltd. Versatile -# Express boards. -# -# Symbol: POWER_RESET_VEXPRESS [=n] -# Type : bool -# Defined at drivers/power/reset/Kconfig:184 -# Prompt: ARM Versatile Express power-off and reset driver -# Depends on: POWER_RESET [=y] && (ARM || ARM64 [=y]) && VEXPRESS_CONFIG [=y]=y -# Location: -# -> Device Drivers -# -> Board level reset or power off (POWER_RESET [=y]) -# -# -# -# CONFIG_POWER_RESET_VEXPRESS is not set -- 2.26.2

3 3

[OS-BUILD PATCH] [redhat] New configs in drivers/power
by CKI Gitlab (via Email Bridge) 14 Apr '21

14 Apr '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/power Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_CHARGER_BQ256XX: Say Y to enable support for the TI BQ256XX battery chargers. The BQ256XX family of devices are highly-integrated, switch-mode battery charge management and system power path management devices for single cell Li-ion and Li-polymer batteries. Symbol: CHARGER_BQ256XX [=n] Type : tristate Defined at drivers/power/supply/Kconfig:658 Prompt: TI BQ256XX battery charger driver Depends on: POWER_SUPPLY [=y] && I2C [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n]) Location: -> Device Drivers -> Power supply class support (POWER_SUPPLY [=y]) Selects: REGMAP_I2C [=m] --- CONFIG_CHARGER_LTC4162L: Say Y to include support for the Analog Devices (Linear Technology) LTC4162-L battery charger connected to I2C. Symbol: CHARGER_LTC4162L [=n] Type : tristate Defined at drivers/power/supply/Kconfig:517 Prompt: LTC4162-L charger Depends on: POWER_SUPPLY [=y] && I2C [=y] Location: -> Device Drivers -> Power supply class support (POWER_SUPPLY [=y]) Selects: REGMAP_I2C [=m] --- Cc: Lenny Szubowicz <lszubowi(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_CHARGER_BQ256XX b/redhat/configs/common/generic/CONFIG_CHARGER_BQ256XX --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_CHARGER_BQ256XX @@ -0,0 +1 @@ +# CONFIG_CHARGER_BQ256XX is not set diff a/redhat/configs/common/generic/CONFIG_CHARGER_LTC4162L b/redhat/configs/common/generic/CONFIG_CHARGER_LTC4162L --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_CHARGER_LTC4162L @@ -0,0 +1 @@ +# CONFIG_CHARGER_LTC4162L is not set diff a/redhat/configs/pending-common/generic/CONFIG_CHARGER_BQ256XX b/redhat/configs/pending-common/generic/CONFIG_CHARGER_BQ256XX --- a/redhat/configs/pending-common/generic/CONFIG_CHARGER_BQ256XX +++ /dev/null @@ -1,20 +0,0 @@ -# CONFIG_CHARGER_BQ256XX: -# -# Say Y to enable support for the TI BQ256XX battery chargers. The -# BQ256XX family of devices are highly-integrated, switch-mode battery -# charge management and system power path management devices for single -# cell Li-ion and Li-polymer batteries. -# -# Symbol: CHARGER_BQ256XX [=n] -# Type : tristate -# Defined at drivers/power/supply/Kconfig:658 -# Prompt: TI BQ256XX battery charger driver -# Depends on: POWER_SUPPLY [=y] && I2C [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n]) -# Location: -# -> Device Drivers -# -> Power supply class support (POWER_SUPPLY [=y]) -# Selects: REGMAP_I2C [=m] -# -# -# -# CONFIG_CHARGER_BQ256XX is not set diff a/redhat/configs/pending-common/generic/CONFIG_CHARGER_LTC4162L b/redhat/configs/pending-common/generic/CONFIG_CHARGER_LTC4162L --- a/redhat/configs/pending-common/generic/CONFIG_CHARGER_LTC4162L +++ /dev/null @@ -1,18 +0,0 @@ -# CONFIG_CHARGER_LTC4162L: -# -# Say Y to include support for the Analog Devices (Linear Technology) -# LTC4162-L battery charger connected to I2C. -# -# Symbol: CHARGER_LTC4162L [=n] -# Type : tristate -# Defined at drivers/power/supply/Kconfig:517 -# Prompt: LTC4162-L charger -# Depends on: POWER_SUPPLY [=y] && I2C [=y] -# Location: -# -> Device Drivers -# -> Power supply class support (POWER_SUPPLY [=y]) -# Selects: REGMAP_I2C [=m] -# -# -# -# CONFIG_CHARGER_LTC4162L is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/919

3 2

[OS-BUILD PATCH] [redhat] New configs in drivers/power
by GitLab Bridge on behalf of jeremycline 14 Apr '21

14 Apr '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_CHARGER_BQ25980: Say Y to enable support for the TI BQ25980, BQ25975 and BQ25960 series of fast battery chargers. Symbol: CHARGER_BQ25980 [=n] Type : tristate Defined at drivers/power/supply/Kconfig:639 Prompt: TI BQ25980 battery charger driver Depends on: POWER_SUPPLY [=y] && I2C [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n]) Location: -> Device Drivers -> Power supply class support (POWER_SUPPLY [=y]) Selects: REGMAP_I2C [=m] --- Cc: Lenny Szubowicz <lszubowi(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_CHARGER_BQ25980 | 1 + .../generic/CONFIG_CHARGER_BQ25980 | 18 ------------------ 2 files changed, 1 insertion(+), 18 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_CHARGER_BQ25980 delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CHARGER_BQ25980 diff --git a/redhat/configs/common/generic/CONFIG_CHARGER_BQ25980 b/redhat/configs/common/generic/CONFIG_CHARGER_BQ25980 new file mode 100644 index 000000000000..65e06f37c92d --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_CHARGER_BQ25980 @@ -0,0 +1 @@ +# CONFIG_CHARGER_BQ25980 is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_CHARGER_BQ25980 b/redhat/configs/pending-common/generic/CONFIG_CHARGER_BQ25980 deleted file mode 100644 index 3c27b8f45b58..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_CHARGER_BQ25980 +++ /dev/null @@ -1,18 +0,0 @@ -# CONFIG_CHARGER_BQ25980: -# -# Say Y to enable support for the TI BQ25980, BQ25975 and BQ25960 -# series of fast battery chargers. -# -# Symbol: CHARGER_BQ25980 [=n] -# Type : tristate -# Defined at drivers/power/supply/Kconfig:639 -# Prompt: TI BQ25980 battery charger driver -# Depends on: POWER_SUPPLY [=y] && I2C [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n]) -# Location: -# -> Device Drivers -# -> Power supply class support (POWER_SUPPLY [=y]) -# Selects: REGMAP_I2C [=m] -# -# -# -# CONFIG_CHARGER_BQ25980 is not set -- GitLab

3 2

[OS-BUILD PATCH] [redhat] New configs in drivers/media
by CKI Gitlab (via Email Bridge) 14 Apr '21

14 Apr '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/media Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_VIDEO_IMX334: This is a Video4Linux2 sensor driver for the Sony IMX334 camera. To compile this driver as a module, choose M here: the module will be called imx334. Symbol: VIDEO_IMX334 [=n] Type : tristate Defined at drivers/media/i2c/Kconfig:816 Prompt: Sony IMX334 sensor support Depends on: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m] Visible if: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y] Location: -> Device Drivers -> Multimedia support (MEDIA_SUPPORT [=m]) -> Media ancillary drivers -> Camera sensor devices Selects: VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y] && V4L2_FWNODE [=n] --- CONFIG_VIDEO_OV5648: This is a Video4Linux2 sensor driver for the OmniVision OV5648 camera. To compile this driver as a module, choose M here: the module will be called ov5648. Symbol: VIDEO_OV5648 [=n] Type : tristate Defined at drivers/media/i2c/Kconfig:953 Prompt: OmniVision OV5648 sensor support Depends on: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m] Visible if: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y] Location: -> Device Drivers -> Multimedia support (MEDIA_SUPPORT [=m]) -> Media ancillary drivers -> Camera sensor devices Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && V4L2_FWNODE [=n] --- CONFIG_VIDEO_OV8865: This is a Video4Linux2 sensor driver for OmniVision OV8865 camera sensor. To compile this driver as a module, choose M here: the module will be called ov8865. Symbol: VIDEO_OV8865 [=n] Type : tristate Defined at drivers/media/i2c/Kconfig:1078 Prompt: OmniVision OV8865 sensor support Depends on: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m] Visible if: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y] Location: -> Device Drivers -> Multimedia support (MEDIA_SUPPORT [=m]) -> Media ancillary drivers -> Camera sensor devices Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && V4L2_FWNODE [=n] --- CONFIG_VIDEO_RDACM21: This driver supports the IMI RDACM21 GMSL camera, used in ADAS systems. This camera should be used in conjunction with a GMSL deserialiser such as the MAX9286. Symbol: VIDEO_RDACM21 [=n] Type : tristate Defined at drivers/media/i2c/Kconfig:1260 Prompt: IMI RDACM21 camera support Depends on: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y] Visible if: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y] && MEDIA_CAMERA_SUPPORT [=y] Location: -> Device Drivers -> Multimedia support (MEDIA_SUPPORT [=m]) -> Media ancillary drivers -> Camera sensor devices Selects: V4L2_FWNODE [=n] && VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y] && VIDEO_MAX9271_LIB [=n] --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_VIDEO_IMX334 b/redhat/configs/common/generic/CONFIG_VIDEO_IMX334 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_VIDEO_IMX334 @@ -0,0 +1 @@ +# CONFIG_VIDEO_IMX334 is not set diff a/redhat/configs/common/generic/CONFIG_VIDEO_OV5648 b/redhat/configs/common/generic/CONFIG_VIDEO_OV5648 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_VIDEO_OV5648 @@ -0,0 +1 @@ +# CONFIG_VIDEO_OV5648 is not set diff a/redhat/configs/common/generic/CONFIG_VIDEO_OV8865 b/redhat/configs/common/generic/CONFIG_VIDEO_OV8865 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_VIDEO_OV8865 @@ -0,0 +1 @@ +# CONFIG_VIDEO_OV8865 is not set diff a/redhat/configs/common/generic/CONFIG_VIDEO_RDACM21 b/redhat/configs/common/generic/CONFIG_VIDEO_RDACM21 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_VIDEO_RDACM21 @@ -0,0 +1 @@ +# CONFIG_VIDEO_RDACM21 is not set diff a/redhat/configs/pending-common/generic/CONFIG_VIDEO_IMX334 b/redhat/configs/pending-common/generic/CONFIG_VIDEO_IMX334 --- a/redhat/configs/pending-common/generic/CONFIG_VIDEO_IMX334 +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_VIDEO_IMX334: -# -# This is a Video4Linux2 sensor driver for the Sony -# IMX334 camera. -# -# To compile this driver as a module, choose M here: the -# module will be called imx334. -# -# Symbol: VIDEO_IMX334 [=n] -# Type : tristate -# Defined at drivers/media/i2c/Kconfig:816 -# Prompt: Sony IMX334 sensor support -# Depends on: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m] -# Visible if: MEDIA_SUPPORT [=m] && OF_GPIO [=y] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y] -# Location: -# -> Device Drivers -# -> Multimedia support (MEDIA_SUPPORT [=m]) -# -> Media ancillary drivers -# -> Camera sensor devices -# Selects: VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y] && V4L2_FWNODE [=n] -# -# -# -# CONFIG_VIDEO_IMX334 is not set diff a/redhat/configs/pending-common/generic/CONFIG_VIDEO_OV5648 b/redhat/configs/pending-common/generic/CONFIG_VIDEO_OV5648 --- a/redhat/configs/pending-common/generic/CONFIG_VIDEO_OV5648 +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_VIDEO_OV5648: -# -# This is a Video4Linux2 sensor driver for the OmniVision -# OV5648 camera. -# -# To compile this driver as a module, choose M here: the -# module will be called ov5648. -# -# Symbol: VIDEO_OV5648 [=n] -# Type : tristate -# Defined at drivers/media/i2c/Kconfig:953 -# Prompt: OmniVision OV5648 sensor support -# Depends on: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m] -# Visible if: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y] -# Location: -# -> Device Drivers -# -> Multimedia support (MEDIA_SUPPORT [=m]) -# -> Media ancillary drivers -# -> Camera sensor devices -# Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && V4L2_FWNODE [=n] -# -# -# -# CONFIG_VIDEO_OV5648 is not set diff a/redhat/configs/pending-common/generic/CONFIG_VIDEO_OV8865 b/redhat/configs/pending-common/generic/CONFIG_VIDEO_OV8865 --- a/redhat/configs/pending-common/generic/CONFIG_VIDEO_OV8865 +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_VIDEO_OV8865: -# -# This is a Video4Linux2 sensor driver for OmniVision -# OV8865 camera sensor. -# -# To compile this driver as a module, choose M here: the -# module will be called ov8865. -# -# Symbol: VIDEO_OV8865 [=n] -# Type : tristate -# Defined at drivers/media/i2c/Kconfig:1078 -# Prompt: OmniVision OV8865 sensor support -# Depends on: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m] -# Visible if: MEDIA_SUPPORT [=m] && I2C [=y] && PM [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y] -# Location: -# -> Device Drivers -# -> Multimedia support (MEDIA_SUPPORT [=m]) -# -> Media ancillary drivers -# -> Camera sensor devices -# Selects: MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && V4L2_FWNODE [=n] -# -# -# -# CONFIG_VIDEO_OV8865 is not set diff a/redhat/configs/pending-common/generic/CONFIG_VIDEO_RDACM21 b/redhat/configs/pending-common/generic/CONFIG_VIDEO_RDACM21 --- a/redhat/configs/pending-common/generic/CONFIG_VIDEO_RDACM21 +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_VIDEO_RDACM21: -# -# This driver supports the IMI RDACM21 GMSL camera, used in -# ADAS systems. -# -# This camera should be used in conjunction with a GMSL -# deserialiser such as the MAX9286. -# -# Symbol: VIDEO_RDACM21 [=n] -# Type : tristate -# Defined at drivers/media/i2c/Kconfig:1260 -# Prompt: IMI RDACM21 camera support -# Depends on: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y] -# Visible if: MEDIA_SUPPORT [=m] && VIDEO_V4L2 [=m] && I2C [=y] && MEDIA_CAMERA_SUPPORT [=y] -# Location: -# -> Device Drivers -# -> Multimedia support (MEDIA_SUPPORT [=m]) -# -> Media ancillary drivers -# -> Camera sensor devices -# Selects: V4L2_FWNODE [=n] && VIDEO_V4L2_SUBDEV_API [=n] && MEDIA_CONTROLLER [=y] && VIDEO_MAX9271_LIB [=n] -# -# -# -# CONFIG_VIDEO_RDACM21 is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/906

2 1

[OS-BUILD PATCH] [redhat] New configs in crypto/Kconfig
by GitLab Bridge on behalf of jeremycline 14 Apr '21

14 Apr '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_CRYPTO_SM2: Generic implementation of the SM2 public key algorithm. It was published by State Encryption Management Bureau, China. as specified by OSCCA GM/T 0003.1-2012 -- 0003.5-2012. References: https://tools.ietf.org/html/draft-shen-sm2-ecdsa-02 http://www.oscca.gov.cn/sca/xxgk/2010-12/17/content_1002386.shtml http://www.gmbz.org.cn/main/bzlb.html Symbol: CRYPTO_SM2 [=n] Type : tristate Defined at crypto/Kconfig:263 Prompt: SM2 algorithm Depends on: CRYPTO [=y] Location: -> Cryptographic API (CRYPTO [=y]) Selects: CRYPTO_SM3 [=n] && CRYPTO_AKCIPHER [=y] && CRYPTO_MANAGER [=y] && MPILIB [=y] && ASN1 [=y] --- CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE: Allow obsolete cryptographic algorithms to be selected that have already been phased out from internal use by the kernel, and are only useful for userspace clients that still rely on them. Symbol: CRYPTO_USER_API_ENABLE_OBSOLETE [=y] Type : bool Defined at crypto/Kconfig:1915 Prompt: Enable obsolete cryptographic algorithms for userspace Depends on: CRYPTO [=y] && CRYPTO_USER_API [=y] Location: -> Cryptographic API (CRYPTO [=y]) --- CONFIG_CRYPTO_USER_API_RNG_CAVP: This option enables extra API for CAVP testing via the user-space interface: resetting of DRBG entropy, and providing Additional Data. This should only be enabled for CAVP testing. You should say no unless you know what this is. Symbol: CRYPTO_USER_API_RNG_CAVP [=n] Type : bool Defined at crypto/Kconfig:1895 Prompt: Enable CAVP testing of DRBG Depends on: CRYPTO [=y] && CRYPTO_USER_API_RNG [=y] && CRYPTO_DRBG [=y] Location: -> Cryptographic API (CRYPTO [=y]) -> User-space interface for random number generator algorithms (CRYPTO_USER_API_RNG [=y]) --- Cc: Herbert Xu <herbert.xu(a)redhat.com> Cc: "David S. Miller" <davem(a)redhat.com> Cc: Ondrej Mosnacek <omosnace(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../configs/common/generic/CONFIG_CRYPTO_SM2 | 1 + .../CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE | 1 + .../generic/CONFIG_CRYPTO_USER_API_RNG_CAVP | 1 + .../pending-common/generic/CONFIG_CRYPTO_SM2 | 23 ------------------- .../CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE | 17 -------------- .../generic/CONFIG_CRYPTO_USER_API_RNG_CAVP | 19 --------------- 6 files changed, 3 insertions(+), 59 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_CRYPTO_SM2 create mode 100644 redhat/configs/common/generic/CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE create mode 100644 redhat/configs/common/generic/CONFIG_CRYPTO_USER_API_RNG_CAVP delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CRYPTO_SM2 delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CRYPTO_USER_API_RNG_CAVP diff --git a/redhat/configs/common/generic/CONFIG_CRYPTO_SM2 b/redhat/configs/common/generic/CONFIG_CRYPTO_SM2 new file mode 100644 index 000000000000..0d8c1b551abf --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_CRYPTO_SM2 @@ -0,0 +1 @@ +# CONFIG_CRYPTO_SM2 is not set diff --git a/redhat/configs/common/generic/CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE b/redhat/configs/common/generic/CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE new file mode 100644 index 000000000000..21d316c28741 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE @@ -0,0 +1 @@ +CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE=y diff --git a/redhat/configs/common/generic/CONFIG_CRYPTO_USER_API_RNG_CAVP b/redhat/configs/common/generic/CONFIG_CRYPTO_USER_API_RNG_CAVP new file mode 100644 index 000000000000..7826178972a9 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_CRYPTO_USER_API_RNG_CAVP @@ -0,0 +1 @@ +# CONFIG_CRYPTO_USER_API_RNG_CAVP is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_CRYPTO_SM2 b/redhat/configs/pending-common/generic/CONFIG_CRYPTO_SM2 deleted file mode 100644 index b577bb249279..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_CRYPTO_SM2 +++ /dev/null @@ -1,23 +0,0 @@ -# CONFIG_CRYPTO_SM2: -# -# Generic implementation of the SM2 public key algorithm. It was -# published by State Encryption Management Bureau, China. -# as specified by OSCCA GM/T 0003.1-2012 -- 0003.5-2012. -# -# References: -# https://tools.ietf.org/html/draft-shen-sm2-ecdsa-02 -# http://www.oscca.gov.cn/sca/xxgk/2010-12/17/content_1002386.shtml -# http://www.gmbz.org.cn/main/bzlb.html -# -# Symbol: CRYPTO_SM2 [=n] -# Type : tristate -# Defined at crypto/Kconfig:263 -# Prompt: SM2 algorithm -# Depends on: CRYPTO [=y] -# Location: -# -> Cryptographic API (CRYPTO [=y]) -# Selects: CRYPTO_SM3 [=n] && CRYPTO_AKCIPHER [=y] && CRYPTO_MANAGER [=y] && MPILIB [=y] && ASN1 [=y] -# -# -# -# CONFIG_CRYPTO_SM2 is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE b/redhat/configs/pending-common/generic/CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE deleted file mode 100644 index b8bda73dbf55..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE +++ /dev/null @@ -1,17 +0,0 @@ -# CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE: -# -# Allow obsolete cryptographic algorithms to be selected that have -# already been phased out from internal use by the kernel, and are -# only useful for userspace clients that still rely on them. -# -# Symbol: CRYPTO_USER_API_ENABLE_OBSOLETE [=y] -# Type : bool -# Defined at crypto/Kconfig:1915 -# Prompt: Enable obsolete cryptographic algorithms for userspace -# Depends on: CRYPTO [=y] && CRYPTO_USER_API [=y] -# Location: -# -> Cryptographic API (CRYPTO [=y]) -# -# -# -CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE=y diff --git a/redhat/configs/pending-common/generic/CONFIG_CRYPTO_USER_API_RNG_CAVP b/redhat/configs/pending-common/generic/CONFIG_CRYPTO_USER_API_RNG_CAVP deleted file mode 100644 index 7e0c667a45ce..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_CRYPTO_USER_API_RNG_CAVP +++ /dev/null @@ -1,19 +0,0 @@ -# CONFIG_CRYPTO_USER_API_RNG_CAVP: -# -# This option enables extra API for CAVP testing via the user-space -# interface: resetting of DRBG entropy, and providing Additional Data. -# This should only be enabled for CAVP testing. You should say -# no unless you know what this is. -# -# Symbol: CRYPTO_USER_API_RNG_CAVP [=n] -# Type : bool -# Defined at crypto/Kconfig:1895 -# Prompt: Enable CAVP testing of DRBG -# Depends on: CRYPTO [=y] && CRYPTO_USER_API_RNG [=y] && CRYPTO_DRBG [=y] -# Location: -# -> Cryptographic API (CRYPTO [=y]) -# -> User-space interface for random number generator algorithms (CRYPTO_USER_API_RNG [=y]) -# -# -# -# CONFIG_CRYPTO_USER_API_RNG_CAVP is not set -- GitLab

13 21

[OS-BUILD PATCH] [redhat] New configs in drivers/net/can
by GitLab Bridge on behalf of jeremycline 14 Apr '21

14 Apr '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_CAN_MCP251XFD: Driver for the Microchip MCP251XFD SPI FD-CAN controller family. Symbol: CAN_MCP251XFD [=n] Type : tristate Defined at drivers/net/can/spi/mcp251xfd/Kconfig:3 Prompt: Microchip MCP251xFD SPI CAN controllers Depends on: NET [=y] && CAN [=m] && CAN_DEV [=m] && SPI [=y] Location: -> Networking support (NET [=y]) -> CAN bus subsystem support (CAN [=m]) -> CAN Device Drivers -> Platform CAN drivers with Netlink support (CAN_DEV [=m]) -> CAN SPI interfaces Selects: REGMAP [=y] --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_CAN_MCP251XFD | 1 + .../generic/CONFIG_CAN_MCP251XFD | 21 ------------------- 2 files changed, 1 insertion(+), 21 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_CAN_MCP251XFD delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CAN_MCP251XFD diff --git a/redhat/configs/common/generic/CONFIG_CAN_MCP251XFD b/redhat/configs/common/generic/CONFIG_CAN_MCP251XFD new file mode 100644 index 000000000000..ba4b9f992ff9 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_CAN_MCP251XFD @@ -0,0 +1 @@ +# CONFIG_CAN_MCP251XFD is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_CAN_MCP251XFD b/redhat/configs/pending-common/generic/CONFIG_CAN_MCP251XFD deleted file mode 100644 index a6fef51cc94b..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_CAN_MCP251XFD +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_CAN_MCP251XFD: -# -# Driver for the Microchip MCP251XFD SPI FD-CAN controller -# family. -# -# Symbol: CAN_MCP251XFD [=n] -# Type : tristate -# Defined at drivers/net/can/spi/mcp251xfd/Kconfig:3 -# Prompt: Microchip MCP251xFD SPI CAN controllers -# Depends on: NET [=y] && CAN [=m] && CAN_DEV [=m] && SPI [=y] -# Location: -# -> Networking support (NET [=y]) -# -> CAN bus subsystem support (CAN [=m]) -# -> CAN Device Drivers -# -> Platform CAN drivers with Netlink support (CAN_DEV [=m]) -# -> CAN SPI interfaces -# Selects: REGMAP [=y] -# -# -# -# CONFIG_CAN_MCP251XFD is not set -- GitLab

4 5

[OS-BUILD PATCH] [redhat] New configs in arch/s390
by GitLab Bridge on behalf of redhat-patchlab 14 Apr '21

14 Apr '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_DEBUG_USER_ASCE: Check on exit to user space that address space control elements are setup correctly. If unsure, say N. Symbol: DEBUG_USER_ASCE [=n] Type : bool Defined at arch/s390/Kconfig.debug:9 Prompt: Debug User ASCE Location: -> Kernel hacking -> s390 Debugging --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_DEBUG_USER_ASCE | 1 + .../generic/CONFIG_DEBUG_USER_ASCE | 18 ------------------ 2 files changed, 1 insertion(+), 18 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_DEBUG_USER_ASCE delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DEBUG_USER_ASCE diff --git a/redhat/configs/common/generic/CONFIG_DEBUG_USER_ASCE b/redhat/configs/common/generic/CONFIG_DEBUG_USER_ASCE new file mode 100644 index 000000000000..8a8327065991 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_DEBUG_USER_ASCE @@ -0,0 +1 @@ +# CONFIG_DEBUG_USER_ASCE is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_DEBUG_USER_ASCE b/redhat/configs/pending-common/generic/CONFIG_DEBUG_USER_ASCE deleted file mode 100644 index aeaa452caae0..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_DEBUG_USER_ASCE +++ /dev/null @@ -1,18 +0,0 @@ -# CONFIG_DEBUG_USER_ASCE: -# -# Check on exit to user space that address space control -# elements are setup correctly. -# -# If unsure, say N. -# -# Symbol: DEBUG_USER_ASCE [=n] -# Type : bool -# Defined at arch/s390/Kconfig.debug:9 -# Prompt: Debug User ASCE -# Location: -# -> Kernel hacking -# -> s390 Debugging -# -# -# -# CONFIG_DEBUG_USER_ASCE is not set -- GitLab

3 4

[OS-BUILD PATCH] [redhat] New configs in fs/fuse
by GitLab Bridge on behalf of jeremycline 14 Apr '21

14 Apr '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_FUSE_DAX: This allows bypassing guest page cache and allows mapping host page cache directly in guest address space. If you want to allow mounting a Virtio Filesystem with the "dax" option, answer Y. Symbol: FUSE_DAX [=y] Type : bool Defined at fs/fuse/Kconfig:42 Prompt: Virtio Filesystem Direct Host Memory Access support Depends on: VIRTIO_FS [=m] && FS_DAX [=y] && DAX_DRIVER [=y] Location: -> File systems -> FUSE (Filesystem in Userspace) support (FUSE_FS [=m]) -> Virtio Filesystem (VIRTIO_FS [=m]) Selects: INTERVAL_TREE [=y] --- Cc: Miklos Szeredi <mszeredi(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/common/generic/CONFIG_FUSE_DAX | 1 + .../pending-common/generic/CONFIG_FUSE_DAX | 22 ------------------- 2 files changed, 1 insertion(+), 22 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_FUSE_DAX delete mode 100644 redhat/configs/pending-common/generic/CONFIG_FUSE_DAX diff --git a/redhat/configs/common/generic/CONFIG_FUSE_DAX b/redhat/configs/common/generic/CONFIG_FUSE_DAX new file mode 100644 index 000000000000..cc453d1c5bc7 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_FUSE_DAX @@ -0,0 +1 @@ +CONFIG_FUSE_DAX=y diff --git a/redhat/configs/pending-common/generic/CONFIG_FUSE_DAX b/redhat/configs/pending-common/generic/CONFIG_FUSE_DAX deleted file mode 100644 index 69992890efd9..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_FUSE_DAX +++ /dev/null @@ -1,22 +0,0 @@ -# CONFIG_FUSE_DAX: -# -# This allows bypassing guest page cache and allows mapping host page -# cache directly in guest address space. -# -# If you want to allow mounting a Virtio Filesystem with the "dax" -# option, answer Y. -# -# Symbol: FUSE_DAX [=y] -# Type : bool -# Defined at fs/fuse/Kconfig:42 -# Prompt: Virtio Filesystem Direct Host Memory Access support -# Depends on: VIRTIO_FS [=m] && FS_DAX [=y] && DAX_DRIVER [=y] -# Location: -# -> File systems -# -> FUSE (Filesystem in Userspace) support (FUSE_FS [=m]) -# -> Virtio Filesystem (VIRTIO_FS [=m]) -# Selects: INTERVAL_TREE [=y] -# -# -# -CONFIG_FUSE_DAX=y -- GitLab

4 4

[OS-BUILD PATCH] [redhat] New configs in drivers/thunderbolt
by GitLab Bridge on behalf of jeremycline 13 Apr '21

13 Apr '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_USB4_DEBUGFS_WRITE: Enables writing to device configuration registers through debugfs interface. Only enable this if you know what you are doing! Never enable this for production systems or distro kernels. Symbol: USB4_DEBUGFS_WRITE [=n] Type : bool Defined at drivers/thunderbolt/Kconfig:21 Prompt: Enable write by debugfs to configuration spaces (DANGEROUS) Depends on: USB4 [=y] Location: -> Device Drivers -> Unified support for USB4 and Thunderbolt (USB4 [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_USB4_DEBUGFS_WRITE | 1 + .../generic/CONFIG_USB4_DEBUGFS_WRITE | 20 ------------------- 2 files changed, 1 insertion(+), 20 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_USB4_DEBUGFS_WRITE delete mode 100644 redhat/configs/pending-common/generic/CONFIG_USB4_DEBUGFS_WRITE diff --git a/redhat/configs/common/generic/CONFIG_USB4_DEBUGFS_WRITE b/redhat/configs/common/generic/CONFIG_USB4_DEBUGFS_WRITE new file mode 100644 index 000000000000..966dff9102ad --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_USB4_DEBUGFS_WRITE @@ -0,0 +1 @@ +# CONFIG_USB4_DEBUGFS_WRITE is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_USB4_DEBUGFS_WRITE b/redhat/configs/pending-common/generic/CONFIG_USB4_DEBUGFS_WRITE deleted file mode 100644 index 4aa0125ab425..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_USB4_DEBUGFS_WRITE +++ /dev/null @@ -1,20 +0,0 @@ -# CONFIG_USB4_DEBUGFS_WRITE: -# -# Enables writing to device configuration registers through -# debugfs interface. -# -# Only enable this if you know what you are doing! Never enable -# this for production systems or distro kernels. -# -# Symbol: USB4_DEBUGFS_WRITE [=n] -# Type : bool -# Defined at drivers/thunderbolt/Kconfig:21 -# Prompt: Enable write by debugfs to configuration spaces (DANGEROUS) -# Depends on: USB4 [=y] -# Location: -# -> Device Drivers -# -> Unified support for USB4 and Thunderbolt (USB4 [=y]) -# -# -# -# CONFIG_USB4_DEBUGFS_WRITE is not set -- GitLab

2 1

[OS-BUILD PATCH] redhat/Makefile.common: Fix 'fatal: Not a valid object name master' error
by GitLab Bridge on behalf of prarit 06 Apr '21

06 Apr '21

From: Prarit Bhargava <prarit(a)redhat.com> Hey everyone, I spent 5-10 mins looking at the 'fatal: Not a valid object name master' error this morning. It comes from the redhat/Makefile.common:45 MERGE_BASE:=$(shell git merge-base HEAD master) There is no master branch so 'git merge-base HEAD master' returns an error with message 'fatal: Not a valid object name master'. If I add a Makefile target to dump the MERGE_BASE, TAG, and SNAPSHOT variables I get MERGE_BASE= TAG=v5.8-rc7-1028-g305981a20220 SNAPSHOT=1 I thought about changing the MERGE_BASE value to MERGE_BASE:=$(shell git merge-base HEAD master >& /dev/null && git merge-base HEAD master || git merge-base HEAD upstream/master) but that seems really clunky. Anyone have a better idea? Maybe it should only be MERGE_BASE:$(git merge-base HEAD upstream/master) ? In any case, after changing the MERGE_BASE line in Makefile.common, and dumping the values the 'fatal' error no longer occurs and MERGE_BASE is set correctly: MERGE_BASE=d3590ebf6f91350192737dd1d1b219c05277f067 TAG=v5.8-rc7-39-gd3590ebf6f91 SNAPSHOT=1 P. ---8<---- Executing some redhat/Makefile targets results in a 'fatal: Not a valid object name master' error. This occurs because MERGE_BASE is calculated against the master branch which may not exist. Check to see if master branch exists and if it doesn't use upstream/master instead. Signed-off-by: Prarit Bhargava <prarit(a)redhat.com> --- redhat/Makefile.common | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/redhat/Makefile.common b/redhat/Makefile.common index 6d048415ba6d..e67f2c9dec50 100644 --- a/redhat/Makefile.common +++ b/redhat/Makefile.common @@ -41,8 +41,7 @@ else VERSION_ON_UPSTREAM:=0 endif ifeq ($(VERSION_ON_UPSTREAM),1) - # master is expected to track mainline. - MERGE_BASE:=$(shell git merge-base HEAD master) + MERGE_BASE:=$(shell git merge-base HEAD master >& /dev/null && git merge-base HEAD master || git merge-base HEAD upstream/master) TAG:=$(shell git describe $(MERGE_BASE)) # a snapshot off of a tagged git is of the form [tag]-[cnt]-g[hash] SNAPSHOT:=$(shell echo $(TAG) | grep -c '\-g') -- GitLab

3 4

[OS-BUILD PATCH] iommu/vt-d: enable INTEL_IDXD_SVM for both fedora and rhel
by Jerry Snitselaar (via Email Bridge) 05 Apr '21

05 Apr '21

From: Jerry Snitselaar <jsnitsel(a)redhat.com> iommu/vt-d: enable INTEL_IDXD_SVM for both fedora and rhel It is already enabled for Fedora, so move to common/generic/x86. Signed-off-by: Jerry Snitselaar <jsnitsel(a)redhat.com> diff a/redhat/configs/fedora/generic/x86/CONFIG_INTEL_IDXD_SVM b/redhat/configs/common/generic/x86/CONFIG_INTEL_IDXD_SVM --- a/redhat/configs/fedora/generic/x86/CONFIG_INTEL_IDXD_SVM +++ b/redhat/configs/common/generic/x86/CONFIG_INTEL_IDXD_SVM diff a/redhat/configs/pending-common/generic/CONFIG_INTEL_IDXD_SVM b/redhat/configs/pending-common/generic/CONFIG_INTEL_IDXD_SVM --- a/redhat/configs/pending-common/generic/CONFIG_INTEL_IDXD_SVM +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_INTEL_IDXD_SVM is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/898

3 3

[OS-BUILD PATCH] docs: Update docs to reflect newer workflow.
by GitLab Bridge on behalf of dzickusrh 02 Apr '21

02 Apr '21

From: Don Zickus <dzickus(a)redhat.com> The workflow has recently changed such that all development is done on the 'os-build' branch. Update the docs to show how easy it is to make a change, commit it, generate the srpm and upload it to koji. Also add it a build dep for making a srpm: patchutils (for filterdiff). Cc: Bastien Nocera <bnocera(a)redhat.com> Cc: Prarit Bhargava <prarit(a)redhat.com> Cc: Justin Forbes <jforbes(a)redhat.com> Signed-off-by: Don Zickus <dzickus(a)redhat.com> --- redhat/docs/index.rst | 16 +++++----------- redhat/docs/repository-layout.rst | 7 ------- redhat/docs/submitting-contributions.rst | 4 ++-- 3 files changed, 7 insertions(+), 20 deletions(-) diff --git a/redhat/docs/index.rst b/redhat/docs/index.rst index 951845cc7be3..b451b9ba49ca 100644 --- a/redhat/docs/index.rst +++ b/redhat/docs/index.rst @@ -36,8 +36,8 @@ Once GitLab finishes forking the repository (this can take a while): git remote add -f upstream git@gitlab.com:cki-project/kernel-ark.git # Install build dependencies - sudo dnf install -y make gcc flex bison bzip2 rpm-build - git checkout upstream/ark-latest + sudo dnf install -y make gcc flex bison bzip2 rpm-build patchutils + git checkout upstream/os-build # If you're on Fedora, you need to run: # ln -s /usr/bin/python3 /usr/libexec/platform-python make dist-srpm @@ -48,18 +48,11 @@ Building an SRPM ---------------- The configuration and build scripts are in the ``os-build`` branch and -are regularly updated to work with Linus's master branch. To build an -SRPM, start by checking out the source tree you'd like to build. In this -example, we'll assume that is Linus's master branch, but it could just -as easily be Fedora's ``ark-patches`` branch (Linus's tree + Fedora -patches) , a sub-system maintainer's tree, or your own creation. +are regularly updated to work with Linus's master branch. :: - git checkout linus/master - git merge -m "Merge branch 'os-build'" os-build - # Fedora carries a patch to alter this setting, so we need to change the configuration to build a vanilla tree. - # If you're targeting RHEL and have brew/rhpkg installed, use "make DIST=.elrdy dist-srpm" instead + git checkout upstream/os-build make dist-srpm You can now build the SRPM however you like: @@ -70,6 +63,7 @@ You can now build the SRPM however you like: mock redhat/rpm/SRPMS/kernel*src.rpm # Build the SRPM in Fedora's Koji koji build --scratch rawhide redhat/rpm/SRPMS/kernel*src.rpm + koji build --scratch eln redhat/rpm/SRPMS/kernel*src.rpm Want to add a patch? Just git-cherry-pick it or apply it with git-am and re-run ``make dist-srpm``. Change configurations in ``redhat/configs/`` diff --git a/redhat/docs/repository-layout.rst b/redhat/docs/repository-layout.rst index 5f6dcb08a1bd..851a2c5d715b 100644 --- a/redhat/docs/repository-layout.rst +++ b/redhat/docs/repository-layout.rst @@ -63,13 +63,6 @@ along with the configuration and build scripts. They can be checked out and built into RPMs. The ``master`` branch points to the latest version of these branches. -rhpatches -~~~~~~~~~ - -This branch is no longer used. Previously, it held the Red Hat patches -for the kernel as a quilt series and remains for historical reasons. -Patch history up to v5.4 is available in this branch. - Tags ---- diff --git a/redhat/docs/submitting-contributions.rst b/redhat/docs/submitting-contributions.rst index 07b25852ec66..65895a9ce49b 100644 --- a/redhat/docs/submitting-contributions.rst +++ b/redhat/docs/submitting-contributions.rst @@ -39,8 +39,8 @@ Patches Quick start: 1. ``git fetch upstream`` -2. ``git checkout upstream/os-build && git checkout -b my-build-change`` -3. Make a change to a file or files in ``redhat/``. +2. ``git checkout -b my-build-change upstream/os-build`` +3. Make a change to a file. 4. Add your changes with ``git add -A``. 5. Commit your changes and write a nice commit message that explains the change: ``git commit -s``. -- GitLab

7 17

[OS-BUILD PATCH] [redhat] New configs in drivers/gpio
by GitLab Bridge on behalf of jeremycline 31 Mar '21

31 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_GPIO_CDEV_V1: Say Y here to support version 1 of the GPIO CDEV ABI. This ABI version is deprecated. Please use the latest ABI for new developments. If unsure, say Y. Symbol: GPIO_CDEV_V1 [=y] Type : bool Defined at drivers/gpio/Kconfig:85 Prompt: Support GPIO ABI Version 1 Depends on: GPIOLIB [=y] && GPIO_CDEV [=y] Location: -> Device Drivers -> GPIO Support (GPIOLIB [=y]) -> Character device (/dev/gpiochipN) support (GPIO_CDEV [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_GPIO_CDEV_V1 | 1 + .../generic/CONFIG_GPIO_CDEV_V1 | 22 ------------------- 2 files changed, 1 insertion(+), 22 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_GPIO_CDEV_V1 delete mode 100644 redhat/configs/pending-common/generic/CONFIG_GPIO_CDEV_V1 diff --git a/redhat/configs/common/generic/CONFIG_GPIO_CDEV_V1 b/redhat/configs/common/generic/CONFIG_GPIO_CDEV_V1 new file mode 100644 index 000000000000..2a4e60a576ae --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_GPIO_CDEV_V1 @@ -0,0 +1 @@ +CONFIG_GPIO_CDEV_V1=y diff --git a/redhat/configs/pending-common/generic/CONFIG_GPIO_CDEV_V1 b/redhat/configs/pending-common/generic/CONFIG_GPIO_CDEV_V1 deleted file mode 100644 index 91a1e3450c38..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_GPIO_CDEV_V1 +++ /dev/null @@ -1,22 +0,0 @@ -# CONFIG_GPIO_CDEV_V1: -# -# Say Y here to support version 1 of the GPIO CDEV ABI. -# -# This ABI version is deprecated. -# Please use the latest ABI for new developments. -# -# If unsure, say Y. -# -# Symbol: GPIO_CDEV_V1 [=y] -# Type : bool -# Defined at drivers/gpio/Kconfig:85 -# Prompt: Support GPIO ABI Version 1 -# Depends on: GPIOLIB [=y] && GPIO_CDEV [=y] -# Location: -# -> Device Drivers -# -> GPIO Support (GPIOLIB [=y]) -# -> Character device (/dev/gpiochipN) support (GPIO_CDEV [=y]) -# -# -# -CONFIG_GPIO_CDEV_V1=y -- GitLab

4 5

[OS-BUILD PATCH] [redhat] New configs in drivers/platform
by CKI Gitlab (via Email Bridge) 29 Mar '21

29 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/platform Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_SURFACE_HOTPLUG: Driver for out-of-band hot-plug event signaling on Microsoft Surface devices with hot-pluggable PCIe cards. This driver is used on Surface Book (2 and 3) devices with a hot-pluggable discrete GPU (dGPU). When not in use, the dGPU on those devices can enter D3cold, which prevents in-band (standard) PCIe hot-plug signaling. Thus, without this driver, detaching the base containing the dGPU will not correctly update the state of the corresponding PCIe device if it is in D3cold. This driver adds support for out-of-band hot-plug notifications, ensuring that the device state is properly updated even when the device in question is in D3cold. Select M or Y here, if you want to (fully) support hot-plugging of dGPU devices on the Surface Book 2 and/or 3 during D3cold. Symbol: SURFACE_HOTPLUG [=n] Type : tristate Defined at drivers/platform/surface/Kconfig:89 Prompt: Surface Hot-Plug Driver Depends on: SURFACE_PLATFORMS [=y] && GPIOLIB [=y] Location: -> Device Drivers -> Microsoft Surface Platform-Specific Device Drivers (SURFACE_PLATFORMS [=y]) --- CONFIG_X86_PLATFORM_DRIVERS_DELL: Say Y here to get to see options for device drivers for various Dell x86 platforms, including vendor-specific laptop extension drivers. This option alone does not add any kernel code. If you say N, all options in this submenu will be skipped and disabled. Symbol: X86_PLATFORM_DRIVERS_DELL [=n] Type : bool Defined at drivers/platform/x86/dell/Kconfig:6 Prompt: Dell X86 Platform Specific Device Drivers Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] Location: -> Device Drivers -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y]) --- Cc: David Arcari <darcari(a)redhat.com> Cc: Mark Langsdorf <mlangsdo(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_SURFACE_HOTPLUG b/redhat/configs/common/generic/CONFIG_SURFACE_HOTPLUG --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_SURFACE_HOTPLUG @@ -0,0 +1 @@ +# CONFIG_SURFACE_HOTPLUG is not set diff a/redhat/configs/common/generic/CONFIG_X86_PLATFORM_DRIVERS_DELL b/redhat/configs/common/generic/CONFIG_X86_PLATFORM_DRIVERS_DELL --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_X86_PLATFORM_DRIVERS_DELL @@ -0,0 +1 @@ +# CONFIG_X86_PLATFORM_DRIVERS_DELL is not set diff a/redhat/configs/pending-common/generic/CONFIG_SURFACE_HOTPLUG b/redhat/configs/pending-common/generic/CONFIG_SURFACE_HOTPLUG --- a/redhat/configs/pending-common/generic/CONFIG_SURFACE_HOTPLUG +++ /dev/null @@ -1,29 +0,0 @@ -# CONFIG_SURFACE_HOTPLUG: -# -# Driver for out-of-band hot-plug event signaling on Microsoft Surface -# devices with hot-pluggable PCIe cards. -# -# This driver is used on Surface Book (2 and 3) devices with a -# hot-pluggable discrete GPU (dGPU). When not in use, the dGPU on those -# devices can enter D3cold, which prevents in-band (standard) PCIe -# hot-plug signaling. Thus, without this driver, detaching the base -# containing the dGPU will not correctly update the state of the -# corresponding PCIe device if it is in D3cold. This driver adds support -# for out-of-band hot-plug notifications, ensuring that the device state -# is properly updated even when the device in question is in D3cold. -# -# Select M or Y here, if you want to (fully) support hot-plugging of -# dGPU devices on the Surface Book 2 and/or 3 during D3cold. -# -# Symbol: SURFACE_HOTPLUG [=n] -# Type : tristate -# Defined at drivers/platform/surface/Kconfig:89 -# Prompt: Surface Hot-Plug Driver -# Depends on: SURFACE_PLATFORMS [=y] && GPIOLIB [=y] -# Location: -# -> Device Drivers -# -> Microsoft Surface Platform-Specific Device Drivers (SURFACE_PLATFORMS [=y]) -# -# -# -# CONFIG_SURFACE_HOTPLUG is not set diff a/redhat/configs/pending-common/generic/CONFIG_X86_PLATFORM_DRIVERS_DELL b/redhat/configs/pending-common/generic/CONFIG_X86_PLATFORM_DRIVERS_DELL --- a/redhat/configs/pending-common/generic/CONFIG_X86_PLATFORM_DRIVERS_DELL +++ /dev/null @@ -1,20 +0,0 @@ -# CONFIG_X86_PLATFORM_DRIVERS_DELL: -# -# Say Y here to get to see options for device drivers for various -# Dell x86 platforms, including vendor-specific laptop extension drivers. -# This option alone does not add any kernel code. -# -# If you say N, all options in this submenu will be skipped and disabled. -# -# Symbol: X86_PLATFORM_DRIVERS_DELL [=n] -# Type : bool -# Defined at drivers/platform/x86/dell/Kconfig:6 -# Prompt: Dell X86 Platform Specific Device Drivers -# Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] -# Location: -# -> Device Drivers -# -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y]) -# -# -# -# CONFIG_X86_PLATFORM_DRIVERS_DELL is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/918

4 4

[OS-BUILD PATCH] [redhat] New configs in fs/Kconfig
by GitLab Bridge on behalf of jeremycline 29 Mar '21

29 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_TMPFS_INODE64: tmpfs has historically used only inode numbers as wide as an unsigned int. In some cases this can cause wraparound, potentially resulting in multiple files with the same inode number on a single device. This option makes tmpfs use the full width of ino_t by default, without needing to specify the inode64 option when mounting. But if a long-lived tmpfs is to be accessed by 32-bit applications so ancient that opening a file larger than 2GiB fails with EINVAL, then the INODE64 config option and inode64 mount option risk operations failing with EOVERFLOW once 33-bit inode numbers are reached. To override this configured default, use the inode32 or inode64 option when mounting. If unsure, say N. Symbol: TMPFS_INODE64 [=n] Type : bool Defined at fs/Kconfig:204 Prompt: Use 64-bit ino_t by default in tmpfs Depends on: TMPFS [=y] && 64BIT [=y] Location: -> File systems -> Pseudo filesystems -> Tmpfs virtual memory file system support (former shm fs) (TMPFS [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_TMPFS_INODE64 | 1 + .../generic/CONFIG_TMPFS_INODE64 | 31 ------------------- 2 files changed, 1 insertion(+), 31 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_TMPFS_INODE64 delete mode 100644 redhat/configs/pending-common/generic/CONFIG_TMPFS_INODE64 diff --git a/redhat/configs/common/generic/CONFIG_TMPFS_INODE64 b/redhat/configs/common/generic/CONFIG_TMPFS_INODE64 new file mode 100644 index 000000000000..cce8a2274ff4 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_TMPFS_INODE64 @@ -0,0 +1 @@ +# CONFIG_TMPFS_INODE64 is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_TMPFS_INODE64 b/redhat/configs/pending-common/generic/CONFIG_TMPFS_INODE64 deleted file mode 100644 index a1c19f28cc41..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_TMPFS_INODE64 +++ /dev/null @@ -1,31 +0,0 @@ -# CONFIG_TMPFS_INODE64: -# -# tmpfs has historically used only inode numbers as wide as an unsigned -# int. In some cases this can cause wraparound, potentially resulting -# in multiple files with the same inode number on a single device. This -# option makes tmpfs use the full width of ino_t by default, without -# needing to specify the inode64 option when mounting. -# -# But if a long-lived tmpfs is to be accessed by 32-bit applications so -# ancient that opening a file larger than 2GiB fails with EINVAL, then -# the INODE64 config option and inode64 mount option risk operations -# failing with EOVERFLOW once 33-bit inode numbers are reached. -# -# To override this configured default, use the inode32 or inode64 -# option when mounting. -# -# If unsure, say N. -# -# Symbol: TMPFS_INODE64 [=n] -# Type : bool -# Defined at fs/Kconfig:204 -# Prompt: Use 64-bit ino_t by default in tmpfs -# Depends on: TMPFS [=y] && 64BIT [=y] -# Location: -# -> File systems -# -> Pseudo filesystems -# -> Tmpfs virtual memory file system support (former shm fs) (TMPFS [=y]) -# -# -# -# CONFIG_TMPFS_INODE64 is not set -- GitLab

4 3

[OS-BUILD PATCH] [redhat] New configs in arch/arm64
by GitLab Bridge on behalf of jeremycline 29 Mar '21

29 Mar '21

From: "CKI@GitLab" <cki-project(a)redhat.com> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_ARM64_BTI: Branch Target Identification (part of the ARMv8.5 Extensions) provides a mechanism to limit the set of locations to which computed branch instructions such as BR or BLR can jump. To make use of BTI on CPUs that support it, say Y. BTI is intended to provide complementary protection to other control flow integrity protection mechanisms, such as the Pointer authentication mechanism provided as part of the ARMv8.3 Extensions. For this reason, it does not make sense to enable this option without also enabling support for pointer authentication. Thus, when enabling this option you should also select ARM64_PTR_AUTH=y. Userspace binaries must also be specifically compiled to make use of this mechanism. If you say N here or the hardware does not support BTI, such binaries can still run, but you get no additional enforcement of branch destinations. Symbol: ARM64_BTI [=y] Type : bool Defined at arch/arm64/Kconfig:1594 Prompt: Branch Target Identification support Location: -> Kernel Features -> ARMv8.5 architectural features --- Cc: Mark Salter <msalter(a)redhat.com> Signed-off-by: CKI@GitLab <cki-project(a)redhat.com> --- .../configs/common/generic/CONFIG_ARM64_BTI | 1 + .../pending-common/generic/CONFIG_ARM64_BTI | 31 ------------------- 2 files changed, 1 insertion(+), 31 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_ARM64_BTI delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ARM64_BTI diff --git a/redhat/configs/common/generic/CONFIG_ARM64_BTI b/redhat/configs/common/generic/CONFIG_ARM64_BTI new file mode 100644 index 000000000000..fb0274de0d49 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_ARM64_BTI @@ -0,0 +1 @@ +CONFIG_ARM64_BTI=y diff --git a/redhat/configs/pending-common/generic/CONFIG_ARM64_BTI b/redhat/configs/pending-common/generic/CONFIG_ARM64_BTI deleted file mode 100644 index 5af4d535b648..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_ARM64_BTI +++ /dev/null @@ -1,31 +0,0 @@ -# CONFIG_ARM64_BTI: -# -# Branch Target Identification (part of the ARMv8.5 Extensions) -# provides a mechanism to limit the set of locations to which computed -# branch instructions such as BR or BLR can jump. -# -# To make use of BTI on CPUs that support it, say Y. -# -# BTI is intended to provide complementary protection to other control -# flow integrity protection mechanisms, such as the Pointer -# authentication mechanism provided as part of the ARMv8.3 Extensions. -# For this reason, it does not make sense to enable this option without -# also enabling support for pointer authentication. Thus, when -# enabling this option you should also select ARM64_PTR_AUTH=y. -# -# Userspace binaries must also be specifically compiled to make use of -# this mechanism. If you say N here or the hardware does not support -# BTI, such binaries can still run, but you get no additional -# enforcement of branch destinations. -# -# Symbol: ARM64_BTI [=y] -# Type : bool -# Defined at arch/arm64/Kconfig:1594 -# Prompt: Branch Target Identification support -# Location: -# -> Kernel Features -# -> ARMv8.5 architectural features -# -# -# -CONFIG_ARM64_BTI=y -- 2.26.2

4 3

[OS-BUILD PATCH] [redhat] New configs in drivers/watchdog
by GitLab Bridge on behalf of jeremycline 29 Mar '21

29 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_ARM_SMC_WATCHDOG: Say Y here to include support for a watchdog timer implemented by the EL3 Secure Monitor on ARM platforms. Requires firmware support. To compile this driver as a module, choose M here: the module will be called arm_smc_wdt. Symbol: ARM_SMC_WATCHDOG [=n] Type : tristate Defined at drivers/watchdog/Kconfig:871 Prompt: ARM Secure Monitor Call based watchdog support Depends on: WATCHDOG [=y] && (ARM || ARM64 [=y]) && OF [=y] && HAVE_ARM_SMCCC [=y] Location: -> Device Drivers -> Watchdog Timer Support (WATCHDOG [=y]) Selects: WATCHDOG_CORE [=y] --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_ARM_SMC_WATCHDOG | 1 + .../generic/CONFIG_ARM_SMC_WATCHDOG | 21 ------------------- 2 files changed, 1 insertion(+), 21 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_ARM_SMC_WATCHDOG delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ARM_SMC_WATCHDOG diff --git a/redhat/configs/common/generic/CONFIG_ARM_SMC_WATCHDOG b/redhat/configs/common/generic/CONFIG_ARM_SMC_WATCHDOG new file mode 100644 index 000000000000..5292578ce994 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_ARM_SMC_WATCHDOG @@ -0,0 +1 @@ +# CONFIG_ARM_SMC_WATCHDOG is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_ARM_SMC_WATCHDOG b/redhat/configs/pending-common/generic/CONFIG_ARM_SMC_WATCHDOG deleted file mode 100644 index af24ce5fab9c..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_ARM_SMC_WATCHDOG +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_ARM_SMC_WATCHDOG: -# -# Say Y here to include support for a watchdog timer -# implemented by the EL3 Secure Monitor on ARM platforms. -# Requires firmware support. -# To compile this driver as a module, choose M here: the -# module will be called arm_smc_wdt. -# -# Symbol: ARM_SMC_WATCHDOG [=n] -# Type : tristate -# Defined at drivers/watchdog/Kconfig:871 -# Prompt: ARM Secure Monitor Call based watchdog support -# Depends on: WATCHDOG [=y] && (ARM || ARM64 [=y]) && OF [=y] && HAVE_ARM_SMCCC [=y] -# Location: -# -> Device Drivers -# -> Watchdog Timer Support (WATCHDOG [=y]) -# Selects: WATCHDOG_CORE [=y] -# -# -# -# CONFIG_ARM_SMC_WATCHDOG is not set -- 2.26.2

3 2

[OS-BUILD PATCH] [redhat] New configs in drivers/dma-buf
by CKI Gitlab (via Email Bridge) 29 Mar '21

29 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/dma-buf Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_DMABUF_DEBUG: This option enables additional checks for DMA-BUF importers and exporters. Specifically it validates that importers do not peek at the underlying struct page when they import a buffer. Symbol: DMABUF_DEBUG [=n] Type : bool Defined at drivers/dma-buf/Kconfig:53 Prompt: DMA-BUF debug checks Location: -> Device Drivers -> DMABUF options --- Cc: Lyude Paul <lyude(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_DMABUF_DEBUG b/redhat/configs/common/generic/CONFIG_DMABUF_DEBUG --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_DMABUF_DEBUG @@ -0,0 +1 @@ +# CONFIG_DMABUF_DEBUG is not set diff a/redhat/configs/pending-common/generic/CONFIG_DMABUF_DEBUG b/redhat/configs/pending-common/generic/CONFIG_DMABUF_DEBUG --- a/redhat/configs/pending-common/generic/CONFIG_DMABUF_DEBUG +++ /dev/null @@ -1,17 +0,0 @@ -# CONFIG_DMABUF_DEBUG: -# -# This option enables additional checks for DMA-BUF importers and -# exporters. Specifically it validates that importers do not peek at the -# underlying struct page when they import a buffer. -# -# Symbol: DMABUF_DEBUG [=n] -# Type : bool -# Defined at drivers/dma-buf/Kconfig:53 -# Prompt: DMA-BUF debug checks -# Location: -# -> Device Drivers -# -> DMABUF options -# -# -# -# CONFIG_DMABUF_DEBUG is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/903

3 2

[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.debug
by GitLab Bridge on behalf of jeremycline 29 Mar '21

29 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_CSD_LOCK_WAIT_DEBUG: This option enables debug prints when CPUs are slow to respond to the smp_call_function*() IPI wrappers. These debug prints include the IPI handler function currently executing (if any) and relevant stack traces. Symbol: CSD_LOCK_WAIT_DEBUG [=n] Type : bool Defined at lib/Kconfig.debug:1380 Prompt: Debugging for csd_lock_wait(), called from smp_call_function*() Depends on: DEBUG_KERNEL [=y] && 64BIT [=y] Location: -> Kernel hacking -> Lock Debugging (spinlocks, mutexes, etc...) --- CONFIG_SCF_TORTURE_TEST: This option provides a kernel module that runs torture tests on the smp_call_function() family of primitives. The kernel module may be built after the fact on the running kernel to be tested, if desired. Symbol: SCF_TORTURE_TEST [=n] Type : tristate Defined at lib/Kconfig.debug:1370 Prompt: torture tests for smp_call_function*() Depends on: DEBUG_KERNEL [=y] Location: -> Kernel hacking -> Lock Debugging (spinlocks, mutexes, etc...) Selects: TORTURE_TEST [=n] --- Cc: Prarit Bhargava <prarit(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG | 1 + .../common/generic/CONFIG_SCF_TORTURE_TEST | 1 + .../generic/CONFIG_CSD_LOCK_WAIT_DEBUG | 19 ------------------ .../generic/CONFIG_SCF_TORTURE_TEST | 20 ------------------- 4 files changed, 2 insertions(+), 39 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG create mode 100644 redhat/configs/common/generic/CONFIG_SCF_TORTURE_TEST delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SCF_TORTURE_TEST diff --git a/redhat/configs/common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG b/redhat/configs/common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG new file mode 100644 index 000000000000..086e41bbfcf8 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG @@ -0,0 +1 @@ +# CONFIG_CSD_LOCK_WAIT_DEBUG is not set diff --git a/redhat/configs/common/generic/CONFIG_SCF_TORTURE_TEST b/redhat/configs/common/generic/CONFIG_SCF_TORTURE_TEST new file mode 100644 index 000000000000..53ebe3b18974 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_SCF_TORTURE_TEST @@ -0,0 +1 @@ +# CONFIG_SCF_TORTURE_TEST is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG b/redhat/configs/pending-common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG deleted file mode 100644 index d2e1af1bda65..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_CSD_LOCK_WAIT_DEBUG +++ /dev/null @@ -1,19 +0,0 @@ -# CONFIG_CSD_LOCK_WAIT_DEBUG: -# -# This option enables debug prints when CPUs are slow to respond -# to the smp_call_function*() IPI wrappers. These debug prints -# include the IPI handler function currently executing (if any) -# and relevant stack traces. -# -# Symbol: CSD_LOCK_WAIT_DEBUG [=n] -# Type : bool -# Defined at lib/Kconfig.debug:1380 -# Prompt: Debugging for csd_lock_wait(), called from smp_call_function*() -# Depends on: DEBUG_KERNEL [=y] && 64BIT [=y] -# Location: -# -> Kernel hacking -# -> Lock Debugging (spinlocks, mutexes, etc...) -# -# -# -# CONFIG_CSD_LOCK_WAIT_DEBUG is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_SCF_TORTURE_TEST b/redhat/configs/pending-common/generic/CONFIG_SCF_TORTURE_TEST deleted file mode 100644 index d22be82b0415..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_SCF_TORTURE_TEST +++ /dev/null @@ -1,20 +0,0 @@ -# CONFIG_SCF_TORTURE_TEST: -# -# This option provides a kernel module that runs torture tests -# on the smp_call_function() family of primitives. The kernel -# module may be built after the fact on the running kernel to -# be tested, if desired. -# -# Symbol: SCF_TORTURE_TEST [=n] -# Type : tristate -# Defined at lib/Kconfig.debug:1370 -# Prompt: torture tests for smp_call_function*() -# Depends on: DEBUG_KERNEL [=y] -# Location: -# -> Kernel hacking -# -> Lock Debugging (spinlocks, mutexes, etc...) -# Selects: TORTURE_TEST [=n] -# -# -# -# CONFIG_SCF_TORTURE_TEST is not set -- GitLab

6 7

[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.kgdb
by GitLab Bridge on behalf of jeremycline 26 Mar '21

26 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_KGDB_HONOUR_BLOCKLIST: If set to Y the debug core will use the kprobe blocklist to identify symbols where it is unsafe to set breakpoints. In particular this disallows instrumentation of functions called during debug trap handling and thus makes it very difficult to inadvertently provoke recursive trap handling. If unsure, say Y. Symbol: KGDB_HONOUR_BLOCKLIST [=y] Type : bool Defined at lib/Kconfig.kgdb:27 Prompt: KGDB: use kprobe blocklist to prohibit unsafe breakpoints Depends on: KGDB [=y] && HAVE_KPROBES [=y] && MODULES [=y] Location: -> Kernel hacking -> Generic Kernel Debugging Instruments -> KGDB: kernel debugger (KGDB [=y]) Selects: KPROBES [=y] --- Cc: Prarit Bhargava <prarit(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../generic/CONFIG_KGDB_HONOUR_BLOCKLIST | 1 + .../generic/CONFIG_KGDB_HONOUR_BLOCKLIST | 24 ------------------- 2 files changed, 1 insertion(+), 24 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST delete mode 100644 redhat/configs/pending-common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST diff --git a/redhat/configs/common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST b/redhat/configs/common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST new file mode 100644 index 000000000000..7da79f661883 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST @@ -0,0 +1 @@ +CONFIG_KGDB_HONOUR_BLOCKLIST=y diff --git a/redhat/configs/pending-common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST b/redhat/configs/pending-common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST deleted file mode 100644 index 224aca014283..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_KGDB_HONOUR_BLOCKLIST: -# -# If set to Y the debug core will use the kprobe blocklist to -# identify symbols where it is unsafe to set breakpoints. -# In particular this disallows instrumentation of functions -# called during debug trap handling and thus makes it very -# difficult to inadvertently provoke recursive trap handling. -# -# If unsure, say Y. -# -# Symbol: KGDB_HONOUR_BLOCKLIST [=y] -# Type : bool -# Defined at lib/Kconfig.kgdb:27 -# Prompt: KGDB: use kprobe blocklist to prohibit unsafe breakpoints -# Depends on: KGDB [=y] && HAVE_KPROBES [=y] && MODULES [=y] -# Location: -# -> Kernel hacking -# -> Generic Kernel Debugging Instruments -# -> KGDB: kernel debugger (KGDB [=y]) -# Selects: KPROBES [=y] -# -# -# -CONFIG_KGDB_HONOUR_BLOCKLIST=y -- GitLab

3 2

[OS-BUILD PATCH] [redhat] New configs in arch/powerpc
by GitLab Bridge on behalf of jeremycline 25 Mar '21

25 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_PPC_PROT_SAO_LPAR: This option adds support for PROT_SAO mappings from userspace inside LPARs on supported CPUs. This may cause issues when performing guest migration from a CPU that supports SAO to one that does not. If unsure, say N here. Symbol: PPC_PROT_SAO_LPAR [=n] Type : bool Defined at arch/powerpc/Kconfig:863 Prompt: Support PROT_SAO mappings in LPARs Depends on: PPC_BOOK3S_64 [=y] Location: -> Kernel options --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_PPC_PROT_SAO_LPAR | 1 + .../generic/CONFIG_PPC_PROT_SAO_LPAR | 21 ------------------- 2 files changed, 1 insertion(+), 21 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_PPC_PROT_SAO_LPAR delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PPC_PROT_SAO_LPAR diff --git a/redhat/configs/common/generic/CONFIG_PPC_PROT_SAO_LPAR b/redhat/configs/common/generic/CONFIG_PPC_PROT_SAO_LPAR new file mode 100644 index 000000000000..bea5ce6ad2b5 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_PPC_PROT_SAO_LPAR @@ -0,0 +1 @@ +# CONFIG_PPC_PROT_SAO_LPAR is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_PPC_PROT_SAO_LPAR b/redhat/configs/pending-common/generic/CONFIG_PPC_PROT_SAO_LPAR deleted file mode 100644 index 88471b97ec8d..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_PPC_PROT_SAO_LPAR +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_PPC_PROT_SAO_LPAR: -# -# This option adds support for PROT_SAO mappings from userspace -# inside LPARs on supported CPUs. -# -# This may cause issues when performing guest migration from -# a CPU that supports SAO to one that does not. -# -# If unsure, say N here. -# -# Symbol: PPC_PROT_SAO_LPAR [=n] -# Type : bool -# Defined at arch/powerpc/Kconfig:863 -# Prompt: Support PROT_SAO mappings in LPARs -# Depends on: PPC_BOOK3S_64 [=y] -# Location: -# -> Kernel options -# -# -# -# CONFIG_PPC_PROT_SAO_LPAR is not set -- GitLab

5 4

[OS-BUILD PATCH] [redhat] New configs in arch/powerpc
by GitLab Bridge on behalf of jeremycline 25 Mar '21

25 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_PPC_RTAS_FILTER: The RTAS syscall API has security issues that could be used to compromise system integrity. This option enforces restrictions on the RTAS calls and arguments passed by userspace programs to mitigate these issues. Say Y unless you know what you are doing and the filter is causing problems for you. Symbol: PPC_RTAS_FILTER [=y] Type : bool Defined at arch/powerpc/Kconfig:991 Prompt: Enable filtering of RTAS syscalls Depends on: PPC_RTAS [=y] Location: -> Kernel options --- Cc: kernel-patches(a)redhat.com Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_PPC_RTAS_FILTER | 1 + .../generic/CONFIG_PPC_RTAS_FILTER | 21 ------------------- 2 files changed, 1 insertion(+), 21 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_PPC_RTAS_FILTER delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PPC_RTAS_FILTER diff --git a/redhat/configs/common/generic/CONFIG_PPC_RTAS_FILTER b/redhat/configs/common/generic/CONFIG_PPC_RTAS_FILTER new file mode 100644 index 000000000000..7470f4d4f0fe --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_PPC_RTAS_FILTER @@ -0,0 +1 @@ +CONFIG_PPC_RTAS_FILTER=y diff --git a/redhat/configs/pending-common/generic/CONFIG_PPC_RTAS_FILTER b/redhat/configs/pending-common/generic/CONFIG_PPC_RTAS_FILTER deleted file mode 100644 index 6105fa8baae5..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_PPC_RTAS_FILTER +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_PPC_RTAS_FILTER: -# -# The RTAS syscall API has security issues that could be used to -# compromise system integrity. This option enforces restrictions on the -# RTAS calls and arguments passed by userspace programs to mitigate -# these issues. -# -# Say Y unless you know what you are doing and the filter is causing -# problems for you. -# -# Symbol: PPC_RTAS_FILTER [=y] -# Type : bool -# Defined at arch/powerpc/Kconfig:991 -# Prompt: Enable filtering of RTAS syscalls -# Depends on: PPC_RTAS [=y] -# Location: -# -> Kernel options -# -# -# -CONFIG_PPC_RTAS_FILTER=y -- GitLab

3 2

[OS-BUILD PATCH] Add git config hook
by GitLab Bridge on behalf of dzickusrh 24 Mar '21

24 Mar '21

From: Don Zickus <dzickus(a)redhat.com> The kernel workflow is adding complexity. Let's hide some of that complexity behind git aliases. Instead of having the developer manually add them all the time, add a make command to 'include' kernel aliases. A new command 'make rh-gitsetup' runs git config --local --add include.path "../redhat/kernel.gitconfig" and adds an include to the local repo's .git/config file. Over time more workflow commands can be added to help developers. Start with a stub config file. V5: text cleanups V4: s/gitconfig/gitsetup V3: expand comment in kernel.gitconfig Signed-off-by: Don Zickus <dzickus(a)redhat.com> --- redhat/Makefile | 6 ++++++ redhat/kernel.gitconfig | 10 ++++++++++ 2 files changed, 16 insertions(+) create mode 100644 redhat/kernel.gitconfig diff --git a/redhat/Makefile b/redhat/Makefile index 0118e5b9e2e9..9236fdb1418a 100644 --- a/redhat/Makefile +++ b/redhat/Makefile @@ -133,6 +133,10 @@ rh-kabi-dw-check: rh-kabi @echo "**** End of KABI DWARF-based comparison report ****" @rm -rf $(KABIDW)/base/$(CURARCH).tmp +rh-gitsetup: + @git config --get include.path | grep -q 'redhat/kernel.gitconfig' || \ + git config --local --add include.path "../redhat/kernel.gitconfig" + rh-configs-commit: rh-configs-prep @cd $(REDHAT)/configs; VERSION=$(KVERSION) ./generate_all_configs.sh $(FLAVOR) 1; \ ./process_configs.sh -z $(PACKAGE_NAME) $(KVERSION) "" $(FLAVOR) @@ -363,6 +367,7 @@ rh-help: @echo ' rh-cross-all-rpms - Build RPMs for all supported archs using a cross compiler.' @echo '' @echo 'Configuration targets:' + @echo ' rh-gitsetup - include redhat/kernel.gitconfig in repo git config' @echo ' rh-configs - Create RHEL config files in redhat/config/.' @echo '' @echo 'For detailed description and full list of targets, run `make rh-full-help`.' @@ -442,6 +447,7 @@ rh-full-help: @echo '' @echo 'Configuration targets:' + @echo ' rh-gitsetup - include redhat/kernel.gitconfig in repo git config' @echo ' rh-configs - Creates config files for RHEL $(RHEL_MAJOR) architectures, cleans them' @echo ' by running make nonint_oldconfig, and copies them to' @echo ' redhat/configs/ directory. This is the target to use for a config!' diff --git a/redhat/kernel.gitconfig b/redhat/kernel.gitconfig new file mode 100644 index 000000000000..6fd63c7ac1aa --- /dev/null +++ b/redhat/kernel.gitconfig @@ -0,0 +1,10 @@ +# The kernel workflow is growing in complexity. Developers can not always +# remember all the nuisances involved. +# This file is meant to aid developers by providing wrappers around some +# parts of the workflow that everyone can use. +# +# Examples include 'aliases' for git-push options or a shortcut for +# executing workflow checks before pushing. +# +# Please do not include personal information here. +[alias] -- 2.26.2

4 5

[OS-BUILD PATCH] [redhat] New configs in drivers/clk
by GitLab Bridge on behalf of redhat-patchlab 24 Mar '21

24 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. --- --- --- --- Cc: Mark Salter <msalter(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/common/generic/CONFIG_CLK_GFM_LPASS_SM8250 | 0 redhat/configs/common/generic/CONFIG_COMMON_CLK_FSL_FLEXSPI | 0 redhat/configs/common/generic/CONFIG_SC_CAMCC_7180 | 0 redhat/configs/common/generic/CONFIG_SDX_GCC_55 | 0 4 files changed, 0 insertions(+), 0 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_CLK_GFM_LPASS_SM8250 create mode 100644 redhat/configs/common/generic/CONFIG_COMMON_CLK_FSL_FLEXSPI create mode 100644 redhat/configs/common/generic/CONFIG_SC_CAMCC_7180 create mode 100644 redhat/configs/common/generic/CONFIG_SDX_GCC_55 diff --git a/redhat/configs/common/generic/CONFIG_CLK_GFM_LPASS_SM8250 b/redhat/configs/common/generic/CONFIG_CLK_GFM_LPASS_SM8250 new file mode 100644 index 000000000000..e69de29bb2d1 diff --git a/redhat/configs/common/generic/CONFIG_COMMON_CLK_FSL_FLEXSPI b/redhat/configs/common/generic/CONFIG_COMMON_CLK_FSL_FLEXSPI new file mode 100644 index 000000000000..e69de29bb2d1 diff --git a/redhat/configs/common/generic/CONFIG_SC_CAMCC_7180 b/redhat/configs/common/generic/CONFIG_SC_CAMCC_7180 new file mode 100644 index 000000000000..e69de29bb2d1 diff --git a/redhat/configs/common/generic/CONFIG_SDX_GCC_55 b/redhat/configs/common/generic/CONFIG_SDX_GCC_55 new file mode 100644 index 000000000000..e69de29bb2d1 -- GitLab

2 1

Is it acceptable to package non-bootable kernels?
by Sergio Lopez 24 Mar '21

24 Mar '21

(This message was originally sent to the Packaging mailing list, where Jason Tibbitts pointed that this is a restriction requested by the Kernel team, and it'll be your opinion the one that will prevail here) Hi, The document "What can be packaged" from "Fedora Packaging Guidelines", in the section "Only one kernel package" [1], states that "Fedora allows only a single kernel package; packages containing alternate kernels are not allowed in the distribution." While not explicitly stated there, I suspect (please correct me if I'm wrong) that statement was written with the idea of preventing alternate kernels that could be used to boot the system. With this premise in mind, I was wondering if non-bootable kernels (that is, kernels in a binary format that's not accepted by a conventional boot loader) would be accepted for packaging. I'm asking this because I would like to package "libkrunfw" [2], a dynamic library that bundles an slightly modified minimalist Linux kernel. The library doesn't really link against the kernel (in the sense that it doesn't resolve any symbols nor calls to any of its code), it just bundles it in a binary format that allows it to be directly injected in a KVM memory region, so it's quite similar to a compressed image format, but for a different use case. "libkrunfw" is consumed by "libkrun" [3], another dynamic library that allows programs to acquire virtualization-based process isolation capabilites. The main user of "libkrun" is "crun", when built with "--with-libkrun", an OCI runtime used by "podman". When all pieces are in place, users can easily run containers with virtualization-based isolation by adding some additional flags to the "podman" command line. I have a COPR repository with pre-built alternative packages as a demonstration [4]. There are a number of reasons why we can't use the kernel that ships with Fedora: - We carry a small number of patches with minor changes that modify the behavior of the kernel for this particular use case. Without them, we can't provide an streamlined UX for running isolated processes. - We need an aggressive minimalist configuration to reduce the memory footprint of each container/isolated process. - We need it to be bundled in a dynamic library, so their contents are mapped into the process memory, enabling programs to switch between namespaces without the need to carry the kernel binary with them. The binary object also needs to be properly aligned to allow direct injection into the KVM memory region without additional copies. Given that "libkrunfw" bundles a kernel image that can't be used for booting the system, would it be acceptable to package it in Fedora? Thanks, Sergio. [1] https://docs.fedoraproject.org/en-US/packaging-guidelines/what-can-be-packa… [2] https://github.com/containers/libkrunfw [3] https://github.com/containers/libkrun [4] https://copr.fedorainfracloud.org/coprs/slp/crun-krun/

6 18

[OS-BUILD PATCH] [redhat] New configs in sound/soc
by GitLab Bridge on behalf of jeremycline 23 Mar '21

23 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_SND_SOC_INTEL_CATPT: Enable support for Intel(R) Haswell and Broadwell platforms with I2S codec present. This is a recommended option. Say Y or m if you have such device. If unsure, say N. Symbol: SND_SOC_INTEL_CATPT [=n] Type : tristate Defined at sound/soc/intel/Kconfig:37 Prompt: Haswell and Broadwell Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_SST_TOPLEVEL [=y] && (ACPI [=y] || COMPILE_TEST [=n]) && DMADEVICES [=y] && SND_DMA_SGBUF [=y] Location: -> Device Drivers -> Sound card support (SOUND [=m]) -> Advanced Linux Sound Architecture (SND [=m]) -> ALSA for SoC audio support (SND_SOC [=m]) -> Intel ASoC SST drivers (SND_SOC_INTEL_SST_TOPLEVEL [=y]) Selects: DW_DMAC_CORE [=y] && SND_SOC_ACPI_INTEL_MATCH [=m] Selected by [n]: - SND_SOC_INTEL_HASWELL [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_SST_TOPLEVEL [=y] --- Cc: Jaroslav Kysela <jkysela(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_SND_SOC_INTEL_CATPT | 1 + .../generic/CONFIG_SND_SOC_INTEL_CATPT | 25 ------------------- 2 files changed, 1 insertion(+), 25 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_SND_SOC_INTEL_CATPT delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SND_SOC_INTEL_CATPT diff --git a/redhat/configs/common/generic/CONFIG_SND_SOC_INTEL_CATPT b/redhat/configs/common/generic/CONFIG_SND_SOC_INTEL_CATPT new file mode 100644 index 000000000000..86874a8f75ef --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_SND_SOC_INTEL_CATPT @@ -0,0 +1 @@ +# CONFIG_SND_SOC_INTEL_CATPT is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_SND_SOC_INTEL_CATPT b/redhat/configs/pending-common/generic/CONFIG_SND_SOC_INTEL_CATPT deleted file mode 100644 index be7a752dde5c..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_SND_SOC_INTEL_CATPT +++ /dev/null @@ -1,25 +0,0 @@ -# CONFIG_SND_SOC_INTEL_CATPT: -# -# Enable support for Intel(R) Haswell and Broadwell platforms -# with I2S codec present. This is a recommended option. -# Say Y or m if you have such device. -# If unsure, say N. -# -# Symbol: SND_SOC_INTEL_CATPT [=n] -# Type : tristate -# Defined at sound/soc/intel/Kconfig:37 -# Prompt: Haswell and Broadwell -# Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_SST_TOPLEVEL [=y] && (ACPI [=y] || COMPILE_TEST [=n]) && DMADEVICES [=y] && SND_DMA_SGBUF [=y] -# Location: -# -> Device Drivers -# -> Sound card support (SOUND [=m]) -# -> Advanced Linux Sound Architecture (SND [=m]) -# -> ALSA for SoC audio support (SND_SOC [=m]) -# -> Intel ASoC SST drivers (SND_SOC_INTEL_SST_TOPLEVEL [=y]) -# Selects: DW_DMAC_CORE [=y] && SND_SOC_ACPI_INTEL_MATCH [=m] -# Selected by [n]: -# - SND_SOC_INTEL_HASWELL [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_SST_TOPLEVEL [=y] -# -# -# -# CONFIG_SND_SOC_INTEL_CATPT is not set -- GitLab

5 4

[OS-BUILD PATCH] [redhat] New configs in drivers/tty
by GitLab Bridge on behalf of redhat-patchlab 23 Mar '21

23 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_SERIAL_BCM63XX: This enables the driver for the onchip UART core found on the following chipsets: BCM33xx (cable modem) BCM63xx/BCM63xxx (DSL) BCM68xx (PON) BCM7xxx (STB) - DOCSIS console Symbol: SERIAL_BCM63XX [=n] Type : tristate Defined at drivers/tty/serial/Kconfig:1117 Prompt: Broadcom BCM63xx/BCM33xx UART support Depends on: TTY [=y] && HAS_IOMEM [=y] && COMMON_CLK [=y] Location: -> Device Drivers -> Character devices -> Enable TTY (TTY [=y]) -> Serial drivers Selects: SERIAL_CORE [=y] --- Cc: John Linville <linville(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_SERIAL_BCM63XX | 1 + .../generic/CONFIG_SERIAL_BCM63XX | 25 ------------------- 2 files changed, 1 insertion(+), 25 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_SERIAL_BCM63XX delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SERIAL_BCM63XX diff --git a/redhat/configs/common/generic/CONFIG_SERIAL_BCM63XX b/redhat/configs/common/generic/CONFIG_SERIAL_BCM63XX new file mode 100644 index 000000000000..514d69a6db4b --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_SERIAL_BCM63XX @@ -0,0 +1 @@ +# CONFIG_SERIAL_BCM63XX is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_SERIAL_BCM63XX b/redhat/configs/pending-common/generic/CONFIG_SERIAL_BCM63XX deleted file mode 100644 index 33db6a7e29ae..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_SERIAL_BCM63XX +++ /dev/null @@ -1,25 +0,0 @@ -# CONFIG_SERIAL_BCM63XX: -# -# This enables the driver for the onchip UART core found on -# the following chipsets: -# -# BCM33xx (cable modem) -# BCM63xx/BCM63xxx (DSL) -# BCM68xx (PON) -# BCM7xxx (STB) - DOCSIS console -# -# Symbol: SERIAL_BCM63XX [=n] -# Type : tristate -# Defined at drivers/tty/serial/Kconfig:1117 -# Prompt: Broadcom BCM63xx/BCM33xx UART support -# Depends on: TTY [=y] && HAS_IOMEM [=y] && COMMON_CLK [=y] -# Location: -# -> Device Drivers -# -> Character devices -# -> Enable TTY (TTY [=y]) -# -> Serial drivers -# Selects: SERIAL_CORE [=y] -# -# -# -# CONFIG_SERIAL_BCM63XX is not set -- GitLab

3 2

[OS-BUILD PATCH] [redhat] New configs in drivers/net/phy
by GitLab Bridge on behalf of jmflinuxtx 23 Mar '21

23 Mar '21

From: "Justin M. Forbes" <jforbes(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_BCM54140_PHY: Support the Broadcom BCM54140 Quad SGMII/QSGMII PHY. This driver also supports the hardware monitoring of this PHY and exposes voltage and temperature sensors. Symbol: BCM54140_PHY [=n] Type : tristate Defined at drivers/net/phy/Kconfig:357 Prompt: Broadcom BCM54140 PHY Depends on: NETDEVICES [=y] && PHYLIB [=y] && (HWMON [=y] || HWMON [=y]=n) Location: -> Device Drivers -> Network device support (NETDEVICES [=y]) -> PHY Device support and infrastructure (PHYLIB [=y]) Selects: BCM_NET_PHYLIB [=m] --- CONFIG_MDIO_IPQ4019: This driver supports the MDIO interface found in Qualcomm IPQ40xx series Soc-s. Symbol: MDIO_IPQ4019 [=n] Type : tristate Defined at drivers/net/phy/Kconfig:160 Prompt: Qualcomm IPQ4019 MDIO interface support Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y] && MDIO_BUS [=y] && HAS_IOMEM [=y] && OF_MDIO [=y] Location: -> Device Drivers -> Network device support (NETDEVICES [=y]) -> MDIO bus device drivers (MDIO_DEVICE [=y]) --- Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org> --- .../common/generic/CONFIG_BCM54140_PHY | 1 + .../common/generic/CONFIG_MDIO_IPQ4019 | 1 + .../generic/CONFIG_BCM54140_PHY | 21 ------------------- .../generic/CONFIG_MDIO_IPQ4019 | 18 ---------------- 4 files changed, 2 insertions(+), 39 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_BCM54140_PHY create mode 100644 redhat/configs/common/generic/CONFIG_MDIO_IPQ4019 delete mode 100644 redhat/configs/pending-common/generic/CONFIG_BCM54140_PHY delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MDIO_IPQ4019 diff --git a/redhat/configs/common/generic/CONFIG_BCM54140_PHY b/redhat/configs/common/generic/CONFIG_BCM54140_PHY new file mode 100644 index 000000000000..ebd2ac9225ca --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_BCM54140_PHY @@ -0,0 +1 @@ +# CONFIG_BCM54140_PHY is not set diff --git a/redhat/configs/common/generic/CONFIG_MDIO_IPQ4019 b/redhat/configs/common/generic/CONFIG_MDIO_IPQ4019 new file mode 100644 index 000000000000..7bdf4704b651 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_MDIO_IPQ4019 @@ -0,0 +1 @@ +# CONFIG_MDIO_IPQ4019 is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_BCM54140_PHY b/redhat/configs/pending-common/generic/CONFIG_BCM54140_PHY deleted file mode 100644 index f86e00bfb361..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_BCM54140_PHY +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_BCM54140_PHY: -# -# Support the Broadcom BCM54140 Quad SGMII/QSGMII PHY. -# -# This driver also supports the hardware monitoring of this PHY and -# exposes voltage and temperature sensors. -# -# Symbol: BCM54140_PHY [=n] -# Type : tristate -# Defined at drivers/net/phy/Kconfig:357 -# Prompt: Broadcom BCM54140 PHY -# Depends on: NETDEVICES [=y] && PHYLIB [=y] && (HWMON [=y] || HWMON [=y]=n) -# Location: -# -> Device Drivers -# -> Network device support (NETDEVICES [=y]) -# -> PHY Device support and infrastructure (PHYLIB [=y]) -# Selects: BCM_NET_PHYLIB [=m] -# -# -# -# CONFIG_BCM54140_PHY is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_MDIO_IPQ4019 b/redhat/configs/pending-common/generic/CONFIG_MDIO_IPQ4019 deleted file mode 100644 index e7792d132188..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_MDIO_IPQ4019 +++ /dev/null @@ -1,18 +0,0 @@ -# CONFIG_MDIO_IPQ4019: -# -# This driver supports the MDIO interface found in Qualcomm -# IPQ40xx series Soc-s. -# -# Symbol: MDIO_IPQ4019 [=n] -# Type : tristate -# Defined at drivers/net/phy/Kconfig:160 -# Prompt: Qualcomm IPQ4019 MDIO interface support -# Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y] && MDIO_BUS [=y] && HAS_IOMEM [=y] && OF_MDIO [=y] -# Location: -# -> Device Drivers -# -> Network device support (NETDEVICES [=y]) -# -> MDIO bus device drivers (MDIO_DEVICE [=y]) -# -# -# -# CONFIG_MDIO_IPQ4019 is not set -- 2.26.2

6 7

[OS-BUILD PATCH] [redhat] New configs in mm/Kconfig
by GitLab Bridge on behalf of redhat-patchlab 23 Mar '21

23 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_GUP_TEST: Provides /sys/kernel/debug/gup_test, which in turn provides a way to make ioctl calls that can launch kernel-based unit tests for the get_user_pages*() and pin_user_pages*() family of API calls. These tests include benchmark testing of the _fast variants of get_user_pages*() and pin_user_pages*(), as well as smoke tests of the non-_fast variants. There is also a sub-test that allows running dump_page() on any of up to eight pages (selected by command line args) within the range of user-space addresses. These pages are either pinned via pin_user_pages*(), or pinned via get_user_pages*(), as specified by other command line arguments. See tools/testing/selftests/vm/gup_test.c Symbol: GUP_TEST [=n] Type : bool Defined at mm/Kconfig:824 Prompt: Enable infrastructure for get_user_pages()-related unit tests Depends on: DEBUG_FS [=y] Location: -> Memory Management options --- Cc: Rafael Aquini <aquini(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/common/generic/CONFIG_GUP_TEST | 1 + .../pending-common/generic/CONFIG_GUP_TEST | 29 ------------------- 2 files changed, 1 insertion(+), 29 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_GUP_TEST delete mode 100644 redhat/configs/pending-common/generic/CONFIG_GUP_TEST diff --git a/redhat/configs/common/generic/CONFIG_GUP_TEST b/redhat/configs/common/generic/CONFIG_GUP_TEST new file mode 100644 index 000000000000..5df4896bb447 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_GUP_TEST @@ -0,0 +1 @@ +# CONFIG_GUP_TEST is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_GUP_TEST b/redhat/configs/pending-common/generic/CONFIG_GUP_TEST deleted file mode 100644 index 11570ef11beb..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_GUP_TEST +++ /dev/null @@ -1,29 +0,0 @@ -# CONFIG_GUP_TEST: -# -# Provides /sys/kernel/debug/gup_test, which in turn provides a way -# to make ioctl calls that can launch kernel-based unit tests for -# the get_user_pages*() and pin_user_pages*() family of API calls. -# -# These tests include benchmark testing of the _fast variants of -# get_user_pages*() and pin_user_pages*(), as well as smoke tests of -# the non-_fast variants. -# -# There is also a sub-test that allows running dump_page() on any -# of up to eight pages (selected by command line args) within the -# range of user-space addresses. These pages are either pinned via -# pin_user_pages*(), or pinned via get_user_pages*(), as specified -# by other command line arguments. -# -# See tools/testing/selftests/vm/gup_test.c -# -# Symbol: GUP_TEST [=n] -# Type : bool -# Defined at mm/Kconfig:824 -# Prompt: Enable infrastructure for get_user_pages()-related unit tests -# Depends on: DEBUG_FS [=y] -# Location: -# -> Memory Management options -# -# -# -# CONFIG_GUP_TEST is not set -- GitLab

3 2

[OS-BUILD PATCH] [redhat] New configs in drivers/input
by GitLab Bridge on behalf of jeremycline 23 Mar '21

23 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_INPUT_IQS269A: Say Y to enable support for the Azoteq IQS269A capacitive touch controller. To compile this driver as a module, choose M here: the module will be called iqs269a. Symbol: INPUT_IQS269A [=n] Type : tristate Defined at drivers/input/misc/Kconfig:721 Prompt: Azoteq IQS269A capacitive touch controller Depends on: !UML && INPUT [=y] && INPUT_MISC [=y] && I2C [=y] Location: -> Device Drivers -> Input device support -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y]) -> Miscellaneous devices (INPUT_MISC [=y]) Selects: REGMAP_I2C [=m] --- CONFIG_TOUCHSCREEN_CY8CTMA140: Say Y here if you have a Cypress CY8CTMA140 capacitive touchscreen also just known as "TMA140" If unsure, say N. To compile this driver as a module, choose M here: the module will be called cy8ctma140. Symbol: TOUCHSCREEN_CY8CTMA140 [=n] Type : tristate Defined at drivers/input/touchscreen/Kconfig:204 Prompt: cy8ctma140 touchscreen Depends on: !UML && INPUT [=y] && INPUT_TOUCHSCREEN [=y] && I2C [=y] Location: -> Device Drivers -> Input device support -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y]) -> Touchscreens (INPUT_TOUCHSCREEN [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_INPUT_IQS269A | 1 + .../generic/CONFIG_TOUCHSCREEN_CY8CTMA140 | 1 + .../generic/CONFIG_INPUT_IQS269A | 23 ------------------ .../generic/CONFIG_TOUCHSCREEN_CY8CTMA140 | 24 ------------------- 4 files changed, 2 insertions(+), 47 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_INPUT_IQS269A create mode 100644 redhat/configs/common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140 delete mode 100644 redhat/configs/pending-common/generic/CONFIG_INPUT_IQS269A delete mode 100644 redhat/configs/pending-common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140 diff --git a/redhat/configs/common/generic/CONFIG_INPUT_IQS269A b/redhat/configs/common/generic/CONFIG_INPUT_IQS269A new file mode 100644 index 000000000000..8b78e198494a --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_INPUT_IQS269A @@ -0,0 +1 @@ +# CONFIG_INPUT_IQS269A is not set diff --git a/redhat/configs/common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140 b/redhat/configs/common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140 new file mode 100644 index 000000000000..fa03c444e54b --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140 @@ -0,0 +1 @@ +# CONFIG_TOUCHSCREEN_CY8CTMA140 is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_INPUT_IQS269A b/redhat/configs/pending-common/generic/CONFIG_INPUT_IQS269A deleted file mode 100644 index 445a42fa0119..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_INPUT_IQS269A +++ /dev/null @@ -1,23 +0,0 @@ -# CONFIG_INPUT_IQS269A: -# -# Say Y to enable support for the Azoteq IQS269A capacitive -# touch controller. -# -# To compile this driver as a module, choose M here: the -# module will be called iqs269a. -# -# Symbol: INPUT_IQS269A [=n] -# Type : tristate -# Defined at drivers/input/misc/Kconfig:721 -# Prompt: Azoteq IQS269A capacitive touch controller -# Depends on: !UML && INPUT [=y] && INPUT_MISC [=y] && I2C [=y] -# Location: -# -> Device Drivers -# -> Input device support -# -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y]) -# -> Miscellaneous devices (INPUT_MISC [=y]) -# Selects: REGMAP_I2C [=m] -# -# -# -# CONFIG_INPUT_IQS269A is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140 b/redhat/configs/pending-common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140 deleted file mode 100644 index bb0283fcabba..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140 +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_TOUCHSCREEN_CY8CTMA140: -# -# Say Y here if you have a Cypress CY8CTMA140 capacitive -# touchscreen also just known as "TMA140" -# -# If unsure, say N. -# -# To compile this driver as a module, choose M here: the -# module will be called cy8ctma140. -# -# Symbol: TOUCHSCREEN_CY8CTMA140 [=n] -# Type : tristate -# Defined at drivers/input/touchscreen/Kconfig:204 -# Prompt: cy8ctma140 touchscreen -# Depends on: !UML && INPUT [=y] && INPUT_TOUCHSCREEN [=y] && I2C [=y] -# Location: -# -> Device Drivers -# -> Input device support -# -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y]) -# -> Touchscreens (INPUT_TOUCHSCREEN [=y]) -# -# -# -# CONFIG_TOUCHSCREEN_CY8CTMA140 is not set -- 2.27.0

5 6

[OS-BUILD PATCH] [redhat] New configs in mm/Kconfig
by GitLab Bridge on behalf of jeremycline 23 Mar '21

23 Mar '21

From: "CKI@GitLab" <cki-project(a)redhat.com> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_ZSMALLOC_PGTABLE_MAPPING: By default, zsmalloc uses a copy-based object mapping method to access allocations that span two pages. However, if a particular architecture (ex, ARM) performs VM mapping faster than copying, then you should select this. This causes zsmalloc to use page table mapping rather than copying for object mapping. You can check speed with zsmalloc benchmark: https://github.com/spartacus06/zsmapbench Symbol: ZSMALLOC_PGTABLE_MAPPING [=n] Type : bool Defined at mm/Kconfig:708 Prompt: Use page table mapping to access object in zsmalloc Depends on: ZSMALLOC [=y]=y Location: -> Memory Management options -> Memory allocator for compressed pages (ZSMALLOC [=y]) --- Signed-off-by: CKI@GitLab <cki-project(a)redhat.com> --- .../generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING | 1 + .../generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING | 23 ------------------- 2 files changed, 1 insertion(+), 23 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING diff --git a/redhat/configs/common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING b/redhat/configs/common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING new file mode 100644 index 000000000000..502c3e374887 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING @@ -0,0 +1 @@ +# CONFIG_ZSMALLOC_PGTABLE_MAPPING is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING b/redhat/configs/pending-common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING deleted file mode 100644 index 2f3d89cf6004..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING +++ /dev/null @@ -1,23 +0,0 @@ -# CONFIG_ZSMALLOC_PGTABLE_MAPPING: -# -# By default, zsmalloc uses a copy-based object mapping method to -# access allocations that span two pages. However, if a particular -# architecture (ex, ARM) performs VM mapping faster than copying, -# then you should select this. This causes zsmalloc to use page table -# mapping rather than copying for object mapping. -# -# You can check speed with zsmalloc benchmark: -# https://github.com/spartacus06/zsmapbench -# -# Symbol: ZSMALLOC_PGTABLE_MAPPING [=n] -# Type : bool -# Defined at mm/Kconfig:708 -# Prompt: Use page table mapping to access object in zsmalloc -# Depends on: ZSMALLOC [=y]=y -# Location: -# -> Memory Management options -# -> Memory allocator for compressed pages (ZSMALLOC [=y]) -# -# -# -# CONFIG_ZSMALLOC_PGTABLE_MAPPING is not set -- 2.26.2

5 4

[OS-BUILD PATCH] New configs in arch/powerpc
by GitLab Bridge on behalf of jeremycline 23 Mar '21

23 Mar '21

From: Jeremy Cline <jcline(a)redhat.com> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_PMU_SYSFS: This option enables sysfs file creation for PMU SPRs like MMCR* and PMC*. Symbol: PMU_SYSFS [=n] Type : bool Defined at arch/powerpc/platforms/Kconfig.cputype:428 Prompt: Create PMU SPRs sysfs file Location: -> Processor support Cc: kernel-patches(a)redhat.com --- redhat/configs/common/generic/CONFIG_PMU_SYSFS | 1 + .../pending-common/generic/CONFIG_PMU_SYSFS | 14 -------------- 2 files changed, 1 insertion(+), 14 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_PMU_SYSFS delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PMU_SYSFS diff --git a/redhat/configs/common/generic/CONFIG_PMU_SYSFS b/redhat/configs/common/generic/CONFIG_PMU_SYSFS new file mode 100644 index 000000000000..d192b509fed0 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_PMU_SYSFS @@ -0,0 +1 @@ +# CONFIG_PMU_SYSFS is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_PMU_SYSFS b/redhat/configs/pending-common/generic/CONFIG_PMU_SYSFS deleted file mode 100644 index 1f1a0f6cec8a..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_PMU_SYSFS +++ /dev/null @@ -1,14 +0,0 @@ -# CONFIG_PMU_SYSFS: -# -# This option enables sysfs file creation for PMU SPRs like MMCR* and PMC*. -# -# Symbol: PMU_SYSFS [=n] -# Type : bool -# Defined at arch/powerpc/platforms/Kconfig.cputype:428 -# Prompt: Create PMU SPRs sysfs file -# Location: -# -> Processor support -# -# -# -# CONFIG_PMU_SYSFS is not set -- GitLab

3 2

[OS-BUILD PATCH] New configs in arch/powerpc
by GitLab Bridge on behalf of jeremycline 23 Mar '21

23 Mar '21

From: Jeremy Cline <jcline(a)redhat.com> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_COMPAT: Enable support for 32bit binaries Symbol: COMPAT [=n] Type : bool Defined at arch/powerpc/Kconfig:268 Depends on: PPC64 Default: y if !CPU_LITTLE_ENDIAN Selects: COMPAT_BINFMT_ELF ARCH_WANT_OLD_COMPAT_IPC COMPAT_OLD_SIGACTION Cc: kernel-patches(a)redhat.com --- redhat/configs/common/generic/powerpc/CONFIG_COMPAT | 1 + .../pending-common/generic/powerpc/CONFIG_COMPAT | 12 ------------ 2 files changed, 1 insertion(+), 12 deletions(-) create mode 100644 redhat/configs/common/generic/powerpc/CONFIG_COMPAT delete mode 100644 redhat/configs/pending-common/generic/powerpc/CONFIG_COMPAT diff --git a/redhat/configs/common/generic/powerpc/CONFIG_COMPAT b/redhat/configs/common/generic/powerpc/CONFIG_COMPAT new file mode 100644 index 000000000000..3e041f1b653b --- /dev/null +++ b/redhat/configs/common/generic/powerpc/CONFIG_COMPAT @@ -0,0 +1 @@ +# CONFIG_COMPAT is not set diff --git a/redhat/configs/pending-common/generic/powerpc/CONFIG_COMPAT b/redhat/configs/pending-common/generic/powerpc/CONFIG_COMPAT deleted file mode 100644 index f59088da33db..000000000000 --- a/redhat/configs/pending-common/generic/powerpc/CONFIG_COMPAT +++ /dev/null @@ -1,12 +0,0 @@ -# CONFIG_COMPAT: -# -# Enable support for 32bit binaries -# -# Symbol: COMPAT [=n] -# Type : bool -# Defined at arch/powerpc/Kconfig:268 -# Depends on: PPC64 -# Default: y if !CPU_LITTLE_ENDIAN -# Selects: COMPAT_BINFMT_ELF, ARCH_WANT_OLD_COMPAT_IPC, COMPAT_OLD_SIGACTION -# -# CONFIG_COMPAT is not set -- GitLab

4 3

[OS-BUILD PATCH] [redhat] New configs in fs/xfs
by GitLab Bridge on behalf of jeremycline 23 Mar '21

23 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_XFS_SUPPORT_V4: The V4 filesystem format lacks certain features that are supported by the V5 format, such as metadata checksumming, strengthened metadata verification, and the ability to store timestamps past the year 2038. Because of this, the V4 format is deprecated. All users should upgrade by backing up their files, reformatting, and restoring from the backup. Administrators and users can detect a V4 filesystem by running xfs_info against a filesystem mountpoint and checking for a string beginning with "crc=". If the string "crc=0" is found, the filesystem is a V4 filesystem. If no such string is found, please upgrade xfsprogs to the latest version and try again. This option will become default N in September 2025. Support for the V4 format will be removed entirely in September 2030. Distributors can say N here to withdraw support earlier. To continue supporting the old V4 format (crc=0), say Y. To close off an attack surface, say N. Symbol: XFS_SUPPORT_V4 [=y] Type : bool Defined at fs/xfs/Kconfig:25 Prompt: Support deprecated V4 (crc=0) format Depends on: BLOCK [=y] && XFS_FS [=m] Location: -> File systems -> XFS filesystem support (XFS_FS [=m]) --- Cc: Brian Foster <bfoster(a)redhat.com> Cc: Carlos Maiolino <cmaiolin(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_XFS_SUPPORT_V4 | 1 + .../generic/CONFIG_XFS_SUPPORT_V4 | 34 ------------------- 2 files changed, 1 insertion(+), 34 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_XFS_SUPPORT_V4 delete mode 100644 redhat/configs/pending-common/generic/CONFIG_XFS_SUPPORT_V4 diff --git a/redhat/configs/common/generic/CONFIG_XFS_SUPPORT_V4 b/redhat/configs/common/generic/CONFIG_XFS_SUPPORT_V4 new file mode 100644 index 000000000000..12315e1fff2b --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_XFS_SUPPORT_V4 @@ -0,0 +1 @@ +CONFIG_XFS_SUPPORT_V4=y diff --git a/redhat/configs/pending-common/generic/CONFIG_XFS_SUPPORT_V4 b/redhat/configs/pending-common/generic/CONFIG_XFS_SUPPORT_V4 deleted file mode 100644 index aeb9b39ac5da..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_XFS_SUPPORT_V4 +++ /dev/null @@ -1,34 +0,0 @@ -# CONFIG_XFS_SUPPORT_V4: -# -# The V4 filesystem format lacks certain features that are supported -# by the V5 format, such as metadata checksumming, strengthened -# metadata verification, and the ability to store timestamps past the -# year 2038. Because of this, the V4 format is deprecated. All users -# should upgrade by backing up their files, reformatting, and restoring -# from the backup. -# -# Administrators and users can detect a V4 filesystem by running -# xfs_info against a filesystem mountpoint and checking for a string -# beginning with "crc=". If the string "crc=0" is found, the -# filesystem is a V4 filesystem. If no such string is found, please -# upgrade xfsprogs to the latest version and try again. -# -# This option will become default N in September 2025. Support for the -# V4 format will be removed entirely in September 2030. Distributors -# can say N here to withdraw support earlier. -# -# To continue supporting the old V4 format (crc=0), say Y. -# To close off an attack surface, say N. -# -# Symbol: XFS_SUPPORT_V4 [=y] -# Type : bool -# Defined at fs/xfs/Kconfig:25 -# Prompt: Support deprecated V4 (crc=0) format -# Depends on: BLOCK [=y] && XFS_FS [=m] -# Location: -# -> File systems -# -> XFS filesystem support (XFS_FS [=m]) -# -# -# -CONFIG_XFS_SUPPORT_V4=y -- GitLab

5 6

[OS-BUILD PATCH] [redhat] New configs in net/bluetooth
by GitLab Bridge on behalf of jmflinuxtx 23 Mar '21

23 Mar '21

From: "Justin M. Forbes" <jforbes(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_BT_MSFTEXT: This options enables support for the Microsoft defined HCI vendor extensions. Symbol: BT_MSFTEXT [=n] Type : bool Defined at net/bluetooth/Kconfig:96 Prompt: Enable Microsoft extensions Depends on: NET [=y] && BT [=m] Location: -> Networking support (NET [=y]) -> Bluetooth subsystem support (BT [=m]) --- Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org> --- redhat/configs/common/generic/CONFIG_BT_MSFTEXT | 1 + .../pending-common/generic/CONFIG_BT_MSFTEXT | 17 ----------------- 2 files changed, 1 insertion(+), 17 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_BT_MSFTEXT delete mode 100644 redhat/configs/pending-common/generic/CONFIG_BT_MSFTEXT diff --git a/redhat/configs/common/generic/CONFIG_BT_MSFTEXT b/redhat/configs/common/generic/CONFIG_BT_MSFTEXT new file mode 100644 index 000000000000..7fae871b2426 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_BT_MSFTEXT @@ -0,0 +1 @@ +# CONFIG_BT_MSFTEXT is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_BT_MSFTEXT b/redhat/configs/pending-common/generic/CONFIG_BT_MSFTEXT deleted file mode 100644 index b93c24c93f7f..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_BT_MSFTEXT +++ /dev/null @@ -1,17 +0,0 @@ -# CONFIG_BT_MSFTEXT: -# -# This options enables support for the Microsoft defined HCI -# vendor extensions. -# -# Symbol: BT_MSFTEXT [=n] -# Type : bool -# Defined at net/bluetooth/Kconfig:96 -# Prompt: Enable Microsoft extensions -# Depends on: NET [=y] && BT [=m] -# Location: -# -> Networking support (NET [=y]) -# -> Bluetooth subsystem support (BT [=m]) -# -# -# -# CONFIG_BT_MSFTEXT is not set -- 2.26.2

5 4

[OS-BUILD PATCH] [redhat] New configs in drivers/net/ethernet/mellanox
by GitLab Bridge on behalf of jmflinuxtx 22 Mar '21

22 Mar '21

From: "Justin M. Forbes" <jforbes(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_MLX5_CLS_ACT: mlx5 ConnectX offloads support for TC classifier action (NET_CLS_ACT), works in both native NIC mode and Switchdev SRIOV mode. Actions get attached to a Hardware offloaded classifiers and are invoked after a successful classification. Actions are used to overwrite the classification result, instantly drop or redirect and/or reformat packets in wire speeds without involving the host cpu. If set to N, TC offloads in both NIC and switchdev modes will be disabled. If unsure, set to Y Symbol: MLX5_CLS_ACT [=y] Type : bool Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:81 Prompt: MLX5 TC classifier action support Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_ESWITCH [=y] && NET_CLS_ACT [=y] Location: -> Device Drivers -> Network device support (NETDEVICES [=y]) -> Ethernet driver support (ETHERNET [=y]) -> Mellanox devices (NET_VENDOR_MELLANOX [=y]) -> Mellanox 5th generation network adapters (ConnectX series) Ethernet support (MLX5_CORE_EN [=y]) -> Mellanox Technologies MLX5 SRIOV E-Switch support (MLX5_ESWITCH [=y]) --- Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org> --- .../common/generic/CONFIG_MLX5_CLS_ACT | 1 + .../generic/CONFIG_MLX5_CLS_ACT | 28 ------------------- 2 files changed, 1 insertion(+), 28 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_MLX5_CLS_ACT delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MLX5_CLS_ACT diff --git a/redhat/configs/common/generic/CONFIG_MLX5_CLS_ACT b/redhat/configs/common/generic/CONFIG_MLX5_CLS_ACT new file mode 100644 index 000000000000..2ff38eef7747 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_MLX5_CLS_ACT @@ -0,0 +1 @@ +CONFIG_MLX5_CLS_ACT=y diff --git a/redhat/configs/pending-common/generic/CONFIG_MLX5_CLS_ACT b/redhat/configs/pending-common/generic/CONFIG_MLX5_CLS_ACT deleted file mode 100644 index 0dd0c3000053..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_MLX5_CLS_ACT +++ /dev/null @@ -1,28 +0,0 @@ -# CONFIG_MLX5_CLS_ACT: -# -# mlx5 ConnectX offloads support for TC classifier action (NET_CLS_ACT), -# works in both native NIC mode and Switchdev SRIOV mode. -# Actions get attached to a Hardware offloaded classifiers and are -# invoked after a successful classification. Actions are used to -# overwrite the classification result, instantly drop or redirect and/or -# reformat packets in wire speeds without involving the host cpu. -# -# If set to N, TC offloads in both NIC and switchdev modes will be disabled. -# If unsure, set to Y -# -# Symbol: MLX5_CLS_ACT [=y] -# Type : bool -# Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:81 -# Prompt: MLX5 TC classifier action support -# Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_ESWITCH [=y] && NET_CLS_ACT [=y] -# Location: -# -> Device Drivers -# -> Network device support (NETDEVICES [=y]) -# -> Ethernet driver support (ETHERNET [=y]) -# -> Mellanox devices (NET_VENDOR_MELLANOX [=y]) -# -> Mellanox 5th generation network adapters (ConnectX series) Ethernet support (MLX5_CORE_EN [=y]) -# -> Mellanox Technologies MLX5 SRIOV E-Switch support (MLX5_ESWITCH [=y]) -# -# -# -CONFIG_MLX5_CLS_ACT=y -- 2.26.2

3 2

[OS-BUILD PATCH] [redhat] New configs in init/Kconfig
by GitLab Bridge on behalf of jeremycline 22 Mar '21

22 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_WATCH_QUEUE: This is a general notification queue for the kernel to pass events to userspace by splicing them into pipes. It can be used in conjunction with watches for key/keyring change notifications and device notifications. See Documentation/watch_queue.rst Symbol: WATCH_QUEUE [=n] Type : bool Defined at init/Kconfig:370 Prompt: General notification queue Location: -> General setup --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../configs/common/generic/CONFIG_WATCH_QUEUE | 1 + .../pending-common/generic/CONFIG_WATCH_QUEUE | 20 ------------------- 2 files changed, 1 insertion(+), 20 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_WATCH_QUEUE delete mode 100644 redhat/configs/pending-common/generic/CONFIG_WATCH_QUEUE diff --git a/redhat/configs/common/generic/CONFIG_WATCH_QUEUE b/redhat/configs/common/generic/CONFIG_WATCH_QUEUE new file mode 100644 index 000000000000..4e2060b85ff3 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_WATCH_QUEUE @@ -0,0 +1 @@ +# CONFIG_WATCH_QUEUE is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_WATCH_QUEUE b/redhat/configs/pending-common/generic/CONFIG_WATCH_QUEUE deleted file mode 100644 index 11707e6429cb..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_WATCH_QUEUE +++ /dev/null @@ -1,20 +0,0 @@ -# CONFIG_WATCH_QUEUE: -# -# -# This is a general notification queue for the kernel to pass events to -# userspace by splicing them into pipes. It can be used in conjunction -# with watches for key/keyring change notifications and device -# notifications. -# -# See Documentation/watch_queue.rst -# -# Symbol: WATCH_QUEUE [=n] -# Type : bool -# Defined at init/Kconfig:370 -# Prompt: General notification queue -# Location: -# -> General setup -# -# -# -# CONFIG_WATCH_QUEUE is not set -- GitLab

6 13

[OS-BUILD PATCH] RHMAINTAINERS: Update DMA Mapping entry
by GitLab Bridge on behalf of prarit 22 Mar '21

22 Mar '21

From: Jerry Snitselaar <jsnitsel(a)redhat.com> I'm taking over the primary role for DMA Mapping so update the maintainers entry. RH-Acked-by: Myron Stowe <mstowe(a)redhat.com RH-Acked-by: Don Dutile <ddutile(a)redhat.com> Cc: Prarit Bhargava <prarit(a)redhat.com> Cc: Donald Dutile <ddutile(a)redhat.com> Signed-off-by: Jerry Snitselaar <jsnitsel(a)redhat.com> --- redhat/rhdocs/MAINTAINERS/RHMAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS b/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS index dda356a9d5e9..df60e8537ff2 100644 --- a/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS +++ b/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS @@ -503,6 +503,7 @@ S: Maintained F: drivers/scsi/hpsa* DMA MAPPING SUPPORT +M: Jerry Snitselaar <jsnitsel(a)redhat.com> M: Donald Dutile <ddutile(a)redhat.com> S: Maintained F: kernel/dma/* -- GitLab

3 2

[OS-BUILD PATCH] redhat: Implement Makefile.dist
by GitLab Bridge on behalf of prarit 22 Mar '21

22 Mar '21

From: Prarit Bhargava <prarit(a)redhat.com> One of the nice things about the RHEL and ARK trees is that commands like 'make dist-configs' and 'make dist-help' can be executed from the top-level linux directory. In the existing code, the makefile includes the top-level linux Makefile if the targets are not dist-* or distg-*. Otherwise the commands are executed with the redhat/Makefile* files. This is clunky and requires the inclusion of the makefile in .gitignore which causes problems when upstream modifies .gitignore. A better approach is to include the code in a top-level Makefile.dist. This change can then be moved upstream for inclusion with a oneline patch to include Makefile.dist. Makefile.dist would not be included in the gitignore file because we want to track changes for the file in our own tree. Move the makefile and Makefile.rhelver code into Makefile.dist, and include Makefile.dist from the top-level Makefile. Signed-off-by: Prarit Bhargava <prarit(a)redhat.com> Cc: dzickus(a)redhat.com Cc: jforbes(a)redhat.com Cc: bcrocker(a)redhat.com --- Makefile | 6 ++---- Makefile.rhelver => Makefile.dist | 19 ++++++++++++++++++- makefile | 16 ---------------- redhat/Makefile | 4 ++-- redhat/Makefile.common | 2 +- redhat/genspec.sh | 2 +- redhat/kernel.spec.template | 2 +- redhat/scripts/new_release.sh | 12 ++++++------ 8 files changed, 31 insertions(+), 32 deletions(-) rename Makefile.rhelver => Makefile.dist (77%) delete mode 100644 makefile diff --git a/Makefile b/Makefile index f3d1dd649d9b..c9a0d4f20808 100644 --- a/Makefile +++ b/Makefile @@ -18,10 +18,6 @@ $(if $(filter __%, $(MAKECMDGOALS)), \ PHONY := __all __all: -# Set RHEL variables -# Use this spot to avoid future merge conflicts -include Makefile.rhelver - # We are using a recursive build, so we need to do a little thinking # to get the ordering right. # @@ -273,6 +269,8 @@ no-sync-config-targets := $(no-dot-config-targets) install %install \ kernelrelease single-targets := %.a %.i %.ko %.lds %.ll %.lst %.mod %.o %.s %.symtypes %/ +-include Makefile.dist + config-build := mixed-build := need-config := 1 diff --git a/Makefile.rhelver b/Makefile.dist similarity index 77% rename from Makefile.rhelver rename to Makefile.dist index 8fceabade7c8..0b4f2d28e7b8 100644 --- a/Makefile.rhelver +++ b/Makefile.dist @@ -12,7 +12,7 @@ RHEL_MINOR = 99 # # Use this spot to avoid future merge conflicts. # Do not trim this comment. -RHEL_RELEASE = 0 +RHEL_RELEASE = 1 # # Early y+1 numbering @@ -43,3 +43,20 @@ ifneq ("$(ZSTREAM)", "yes") RHEL_RELEASE:=$(RHEL_RELEASE).$(EARLY_YRELEASE) endif endif + +no-dot-config-targets += dist-% distg-% + +ifneq ($(filter dist-% distg-%,$(MAKECMDGOALS)),) +_OUTPUT := "." +# this section is needed in order to make O= to work +ifeq ("$(origin O)", "command line") + _OUTPUT := "$(abspath $(O))" + _EXTRA_ARGS := O=$(_OUTPUT) +endif +endif + +dist-%:: + $(MAKE) -C redhat $(@) $(_EXTRA_ARGS) + +distg-%:: + $(MAKE) -C redhat $(@) $(_EXTRA_ARGS) diff --git a/makefile b/makefile deleted file mode 100644 index 819ac9a5cd60..000000000000 --- a/makefile +++ /dev/null @@ -1,16 +0,0 @@ -ifeq ($(filter dist-% distg-%,$(MAKECMDGOALS)),) - include Makefile -endif - -_OUTPUT := "." -# this section is needed in order to make O= to work -ifeq ("$(origin O)", "command line") - _OUTPUT := "$(abspath $(O))" - _EXTRA_ARGS := O=$(_OUTPUT) -endif -dist-%:: - $(MAKE) -C redhat $(@) $(_EXTRA_ARGS) - -distg-%:: - $(MAKE) -C redhat $(@) $(_EXTRA_ARGS) - diff --git a/redhat/Makefile b/redhat/Makefile index 61dcc522fbc6..8c6a3a510768 100644 --- a/redhat/Makefile +++ b/redhat/Makefile @@ -256,7 +256,7 @@ sources-rh: $(TARBALL) configs/process_configs.sh \ parallel_xz.sh \ generate_bls_conf.sh \ - ../Makefile.rhelver \ + ../Makefile.dist \ README.rst \ $(SOURCES)/ @for KABIARCH in $(ARCH_LIST); do \ @@ -308,7 +308,7 @@ dist-release-finish: setup-source @git add $(REDHAT)/$(CHANGELOG) @echo $(MARKER) > $(REDHAT)/marker @git add $(REDHAT)/marker - @git commit -s ../Makefile.rhelver $(REDHAT)/marker $(REDHAT)/$(CHANGELOG) $(PACKAGE_NAME).spec.template -m "[redhat] $(PACKAGE_NAME)-$(STAMP_VERSION)-$(PREBUILD)$(BUILD)$(BUILDID)" + @git commit -s ../Makefile.dist $(REDHAT)/marker $(REDHAT)/$(CHANGELOG) $(PACKAGE_NAME).spec.template -m "[redhat] $(PACKAGE_NAME)-$(STAMP_VERSION)-$(PREBUILD)$(BUILD)$(BUILDID)" @$(MAKE) dist-configs @$(MAKE) dist-kabi @$(MAKE) dist-kabi-dup diff --git a/redhat/Makefile.common b/redhat/Makefile.common index 6d048415ba6d..d4e68369fb05 100644 --- a/redhat/Makefile.common +++ b/redhat/Makefile.common @@ -1,6 +1,6 @@ TOPDIR:=$(shell git rev-parse --show-toplevel) REDHAT:=$(TOPDIR)/redhat -include $(TOPDIR)/Makefile.rhelver +include $(TOPDIR)/Makefile.dist RPMBUILD := $(shell if [ -x "/usr/bin/rpmbuild" ]; then echo rpmbuild; \ else echo rpm; fi) diff --git a/redhat/genspec.sh b/redhat/genspec.sh index b72dffe14729..1cd9095a69ea 100755 --- a/redhat/genspec.sh +++ b/redhat/genspec.sh @@ -253,7 +253,7 @@ if [ "$SINGLE_TARBALL" = 0 ]; then ":(exclude,top).gitignore" \ ":(exclude,top).gitlab-ci.yml" \ ":(exclude,top)makefile" \ - ":(exclude,top)Makefile.rhelver" \ + ":(exclude,top)Makefile.dist" \ ":(exclude,top)redhat") for c in $COMMITS; do patch=$(git format-patch --zero-commit -1 "$c") diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template index d47c9cce8a0e..93fa8c2985b1 100644 --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -569,7 +569,7 @@ BuildRequires: asciidoc # xzcat -qq ${TARBALL} | git get-tar-commit-id Source0: linux-%%TARBALL_VERSION%%.tar.xz -Source1: Makefile.rhelver +Source1: Makefile.dist # Name of the packaged file containing signing key diff --git a/redhat/scripts/new_release.sh b/redhat/scripts/new_release.sh index 1e4c7bb1dc86..f1025f458d04 100755 --- a/redhat/scripts/new_release.sh +++ b/redhat/scripts/new_release.sh @@ -13,7 +13,7 @@ if [ -s "$RHPATH/linux-kernel-test.patch" ]; then exit 1; fi -RELEASE=$(sed -n -e 's/^RHEL_RELEASE\ =\ $.*$/\1/p' $RHPATH/../Makefile.rhelver) +RELEASE=$(sed -n -e 's/^RHEL_RELEASE\ =\ $.*$/\1/p' $RHPATH/../Makefile.dist) YVER=$(echo $RELEASE | cut -d "." -f 1) YVER=${YVER:=$RELEASE} @@ -26,15 +26,15 @@ if [ "$ZSTREAM_FLAG" == "no" ]; then if [ "$YSTREAM_FLAG" == "yes" ]; then NEW_RELEASE="$[RELEASE + 1]"; else - EARLY_YBUILD=$(sed -n -e 's/^EARLY_YBUILD:=$.*$/\1/p' $RHPATH/../Makefile.rhelver); - EARLY_YRELEASE=$(sed -n -e 's/^EARLY_YRELEASE:=$.*$/\1/p' $RHPATH/../Makefile.rhelver); + EARLY_YBUILD=$(sed -n -e 's/^EARLY_YBUILD:=$.*$/\1/p' $RHPATH/../Makefile.dist); + EARLY_YRELEASE=$(sed -n -e 's/^EARLY_YRELEASE:=$.*$/\1/p' $RHPATH/../Makefile.dist); if [ "$EARLY_YBUILD" != "$RELEASE" ]; then NEW_EARLY_YRELEASE=1; else NEW_EARLY_YRELEASE="$[EARLY_YRELEASE + 1]"; fi - sed -i -e "s/^EARLY_YBUILD:=$EARLY_YBUILD/EARLY_YBUILD:=$RELEASE/" $RHPATH/../Makefile.rhelver; - sed -i -e "s/^EARLY_YRELEASE:=$EARLY_YRELEASE/EARLY_YRELEASE:=$NEW_EARLY_YRELEASE/" $RHPATH/../Makefile.rhelver; + sed -i -e "s/^EARLY_YBUILD:=$EARLY_YBUILD/EARLY_YBUILD:=$RELEASE/" $RHPATH/../Makefile.dist; + sed -i -e "s/^EARLY_YRELEASE:=$EARLY_YRELEASE/EARLY_YRELEASE:=$NEW_EARLY_YRELEASE/" $RHPATH/../Makefile.dist; NEW_RELEASE=$RELEASE; fi elif [ "$ZSTREAM_FLAG" == "yes" ]; then @@ -46,5 +46,5 @@ else exit 1; fi -sed -i -e "s/RHEL_RELEASE\ =.*/RHEL_RELEASE\ =\ $NEW_RELEASE/" $RHPATH/../Makefile.rhelver; +sed -i -e "s/RHEL_RELEASE\ =.*/RHEL_RELEASE\ =\ $NEW_RELEASE/" $RHPATH/../Makefile.dist; -- GitLab

4 6

[OS-BUILD PATCHv2] [redhat] spec: Add %bcond_with toolchain_clang option
by Tom Stellard (via Email Bridge) 22 Mar '21

22 Mar '21

From: Tom Stellard <tstellar(a)redhat.com> [redhat] spec: Add %bcond_with toolchain_clang option This option can be enabled by passing --with toolchain_clang to rpmbuild or mock. Enabling this option will cause the kernel to be built with clang instead of gcc. Signed-off-by: Tom Stellard <tstellar(a)redhat.com> diff a/redhat/kernel.spec.template b/redhat/kernel.spec.template --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -6,6 +6,12 @@ # Disable LTO in userspace packages. %global _lto_cflags %{nil} +# Option to enable compiling with clang instead of gcc. +%bcond_with toolchain_clang + +%if %{with toolchain_clang} +%global toolchain clang +%endif # Cross compile on copr for arm # See https://bugzilla.redhat.com/1879599 @@ -228,6 +234,10 @@ Summary: The Linux kernel %define make_opts -s %endif +%if %{with toolchain_clang} +%global make_opts %{make_opts} HOSTCC=clang CC=clang +%endif + # turn off debug kernel and kabichk for gcov builds %if %{with_gcov} %define with_debug 0 @@ -432,6 +442,14 @@ Summary: The Linux kernel %define with_configchecks 0 %endif +# Setting the compiler to clang enables some different config options +# than what is expected, so disable this check for now. +# TODO: What's the best way to fix this? Do wee need a different set of +# configs for clang? +%if %{with toolchain_clang} +%define with_configchecks 0 +%endif + # To temporarily exclude an architecture from being built, add it to # %%nobuildarches. Do _NOT_ use the ExclusiveArch: line, because if we # don't build kernel-headers then the new build system will no longer let @@ -596,6 +614,10 @@ BuildRequires: xmlto BuildRequires: asciidoc %endif +%if %{with toolchain_clang} +BuildRequires: clang +%endif + # Because this is the kernel, it's hard to get a single upstream URL # to represent the base without needing to do a bunch of patching. This # tarball is generated from a src-git tree. If you want to see the -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/894

4 8

[OS-BUILD PATCH] [redhat] New configs in drivers/pinctrl
by CKI Gitlab (via Email Bridge) 22 Mar '21

22 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/pinctrl Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_PINCTRL_SC8180X: This is the pinctrl, pinmux, pinconf and gpiolib driver for the Qualcomm Technologies Inc TLMM block found on the Qualcomm Technologies Inc SC8180x platform. Symbol: PINCTRL_SC8180X [=n] Type : tristate Defined at drivers/pinctrl/qcom/Kconfig:223 Prompt: Qualcomm Technologies Inc SC8180x pin controller driver Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y] Location: -> Device Drivers -> Pin controllers (PINCTRL [=y]) Selects: PINCTRL_MSM [=n] --- CONFIG_PINCTRL_SM8350: This is the pinctrl, pinmux, pinconf and gpiolib driver for the Qualcomm Technologies Inc TLMM block found on the Qualcomm Technologies Inc SM8350 platform. Symbol: PINCTRL_SM8350 [=n] Type : tristate Defined at drivers/pinctrl/qcom/Kconfig:277 Prompt: Qualcomm Technologies Inc SM8350 pin controller driver Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y] Location: -> Device Drivers -> Pin controllers (PINCTRL [=y]) Selects: PINCTRL_MSM [=n] --- Cc: Brian Masney <bmasney(a)redhat.com> Cc: David Arcari <darcari(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_PINCTRL_SC8180X b/redhat/configs/common/generic/CONFIG_PINCTRL_SC8180X --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_PINCTRL_SC8180X @@ -0,0 +1 @@ +# CONFIG_PINCTRL_SC8180X is not set diff a/redhat/configs/common/generic/CONFIG_PINCTRL_SM8350 b/redhat/configs/common/generic/CONFIG_PINCTRL_SM8350 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_PINCTRL_SM8350 @@ -0,0 +1 @@ +# CONFIG_PINCTRL_SM8350 is not set diff a/redhat/configs/pending-common/generic/CONFIG_PINCTRL_SC8180X b/redhat/configs/pending-common/generic/CONFIG_PINCTRL_SC8180X --- a/redhat/configs/pending-common/generic/CONFIG_PINCTRL_SC8180X +++ /dev/null @@ -1,19 +0,0 @@ -# CONFIG_PINCTRL_SC8180X: -# -# This is the pinctrl, pinmux, pinconf and gpiolib driver for the -# Qualcomm Technologies Inc TLMM block found on the Qualcomm -# Technologies Inc SC8180x platform. -# -# Symbol: PINCTRL_SC8180X [=n] -# Type : tristate -# Defined at drivers/pinctrl/qcom/Kconfig:223 -# Prompt: Qualcomm Technologies Inc SC8180x pin controller driver -# Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y] -# Location: -# -> Device Drivers -# -> Pin controllers (PINCTRL [=y]) -# Selects: PINCTRL_MSM [=n] -# -# -# -# CONFIG_PINCTRL_SC8180X is not set diff a/redhat/configs/pending-common/generic/CONFIG_PINCTRL_SM8350 b/redhat/configs/pending-common/generic/CONFIG_PINCTRL_SM8350 --- a/redhat/configs/pending-common/generic/CONFIG_PINCTRL_SM8350 +++ /dev/null @@ -1,19 +0,0 @@ -# CONFIG_PINCTRL_SM8350: -# -# This is the pinctrl, pinmux, pinconf and gpiolib driver for the -# Qualcomm Technologies Inc TLMM block found on the Qualcomm -# Technologies Inc SM8350 platform. -# -# Symbol: PINCTRL_SM8350 [=n] -# Type : tristate -# Defined at drivers/pinctrl/qcom/Kconfig:277 -# Prompt: Qualcomm Technologies Inc SM8350 pin controller driver -# Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y] -# Location: -# -> Device Drivers -# -> Pin controllers (PINCTRL [=y]) -# Selects: PINCTRL_MSM [=n] -# -# -# -# CONFIG_PINCTRL_SM8350 is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/917

2 1

[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.debug
by GitLab Bridge on behalf of redhat-patchlab 18 Mar '21

18 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_HARDLOCKUP_DETECTOR: Say Y here to enable the kernel to act as a watchdog to detect hard lockups. Hardlockups are bugs that cause the CPU to loop in kernel mode for more than 10 seconds, without letting other interrupts have a chance to run. The current stack trace is displayed upon detection and the system will stay locked up. Symbol: HARDLOCKUP_DETECTOR [=n] Type : bool Defined at lib/Kconfig.debug:1000 Prompt: Detect Hard Lockups Depends on: DEBUG_KERNEL [=y] && !S390 && (HAVE_HARDLOCKUP_DETECTOR_PERF [=y] || HAVE_HARDLOCKUP_DETECTOR_ARCH [=n]) Location: -> Kernel hacking -> Debug Oops, Lockups and Hangs Selects: LOCKUP_DETECTOR [=y] && HARDLOCKUP_DETECTOR_PERF [=n] && HARDLOCKUP_DETECTOR_ARCH --- Cc: Prarit Bhargava <prarit(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_HARDLOCKUP_DETECTOR | 1 + .../generic/CONFIG_HARDLOCKUP_DETECTOR | 23 ------------------- 2 files changed, 1 insertion(+), 23 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_HARDLOCKUP_DETECTOR delete mode 100644 redhat/configs/pending-common/generic/CONFIG_HARDLOCKUP_DETECTOR diff --git a/redhat/configs/common/generic/CONFIG_HARDLOCKUP_DETECTOR b/redhat/configs/common/generic/CONFIG_HARDLOCKUP_DETECTOR new file mode 100644 index 000000000000..32d4a56dd961 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_HARDLOCKUP_DETECTOR @@ -0,0 +1 @@ +# CONFIG_HARDLOCKUP_DETECTOR is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_HARDLOCKUP_DETECTOR b/redhat/configs/pending-common/generic/CONFIG_HARDLOCKUP_DETECTOR deleted file mode 100644 index cd74a33e67ea..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_HARDLOCKUP_DETECTOR +++ /dev/null @@ -1,23 +0,0 @@ -# CONFIG_HARDLOCKUP_DETECTOR: -# -# Say Y here to enable the kernel to act as a watchdog to detect -# hard lockups. -# -# Hardlockups are bugs that cause the CPU to loop in kernel mode -# for more than 10 seconds, without letting other interrupts have a -# chance to run. The current stack trace is displayed upon detection -# and the system will stay locked up. -# -# Symbol: HARDLOCKUP_DETECTOR [=n] -# Type : bool -# Defined at lib/Kconfig.debug:1000 -# Prompt: Detect Hard Lockups -# Depends on: DEBUG_KERNEL [=y] && !S390 && (HAVE_HARDLOCKUP_DETECTOR_PERF [=y] || HAVE_HARDLOCKUP_DETECTOR_ARCH [=n]) -# Location: -# -> Kernel hacking -# -> Debug Oops, Lockups and Hangs -# Selects: LOCKUP_DETECTOR [=y] && HARDLOCKUP_DETECTOR_PERF [=n] && HARDLOCKUP_DETECTOR_ARCH -# -# -# -# CONFIG_HARDLOCKUP_DETECTOR is not set -- GitLab

3 2

[OS-BUILD PATCH] [redhat] New configs in drivers/md
by GitLab Bridge on behalf of redhat-patchlab 16 Mar '21

16 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_DM_MULTIPATH_IOA: This path selector selects the path based on the CPU the IO is executed on and the CPU to path mapping setup at path addition time. If unsure, say N. Symbol: DM_MULTIPATH_IOA [=n] Type : tristate Defined at drivers/md/Kconfig:466 Prompt: I/O Path Selector based on CPU submission Depends on: MD [=y] && DM_MULTIPATH [=m] Location: -> Device Drivers -> Multiple devices driver support (RAID and LVM) (MD [=y]) -> Device mapper support (BLK_DEV_DM [=m]) -> Multipath target (DM_MULTIPATH [=m]) --- Cc: Nigel Croxon <ncroxon(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_DM_MULTIPATH_IOA | 1 + .../generic/CONFIG_DM_MULTIPATH_IOA | 21 ------------------- 2 files changed, 1 insertion(+), 21 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_DM_MULTIPATH_IOA delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DM_MULTIPATH_IOA diff --git a/redhat/configs/common/generic/CONFIG_DM_MULTIPATH_IOA b/redhat/configs/common/generic/CONFIG_DM_MULTIPATH_IOA new file mode 100644 index 000000000000..9dbcf92fa81e --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_DM_MULTIPATH_IOA @@ -0,0 +1 @@ +# CONFIG_DM_MULTIPATH_IOA is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_DM_MULTIPATH_IOA b/redhat/configs/pending-common/generic/CONFIG_DM_MULTIPATH_IOA deleted file mode 100644 index 83a1a727f1bd..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_DM_MULTIPATH_IOA +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_DM_MULTIPATH_IOA: -# -# This path selector selects the path based on the CPU the IO is -# executed on and the CPU to path mapping setup at path addition time. -# -# If unsure, say N. -# -# Symbol: DM_MULTIPATH_IOA [=n] -# Type : tristate -# Defined at drivers/md/Kconfig:466 -# Prompt: I/O Path Selector based on CPU submission -# Depends on: MD [=y] && DM_MULTIPATH [=m] -# Location: -# -> Device Drivers -# -> Multiple devices driver support (RAID and LVM) (MD [=y]) -# -> Device mapper support (BLK_DEV_DM [=m]) -# -> Multipath target (DM_MULTIPATH [=m]) -# -# -# -# CONFIG_DM_MULTIPATH_IOA is not set -- GitLab

3 3

[OS-BUILD PATCH 0/10] Arm ark/fedora config unification
by Jeremy Linton (via Email Bridge) 15 Mar '21

15 Mar '21

From: Jeremy Linton on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/884 Enable some arm options globally across ark & fedora. Some of these options like coresight are already enabled in fedora and should be enabled in ark, are enabled=y and should be =m, or are the same (efi options) in both configs and should be moved into the common directory. general platform drivers, etc have been left alone.

4 11

[OS-BUILD PATCH] [redhat] New configs in drivers/nvme
by GitLab Bridge on behalf of jeremycline 15 Mar '21

15 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_NVME_TARGET_PASSTHRU: This enables target side NVMe passthru controller support for the NVMe Over Fabrics protocol. It allows for hosts to manage and directly access an actual NVMe controller residing on the target side, incuding executing Vendor Unique Commands. If unsure, say N. Symbol: NVME_TARGET_PASSTHRU [=n] Type : bool Defined at drivers/nvme/target/Kconfig:19 Prompt: NVMe Target Passthrough support Depends on: NVME_TARGET [=m] && (NVME_CORE [=m]=y || NVME_CORE [=m]=NVME_TARGET [=m]) Location: -> Device Drivers -> NVME Support -> NVMe Target support (NVME_TARGET [=m]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../generic/CONFIG_NVME_TARGET_PASSTHRU | 1 + .../generic/CONFIG_NVME_TARGET_PASSTHRU | 22 ------------------- 2 files changed, 1 insertion(+), 22 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_NVME_TARGET_PASSTHRU delete mode 100644 redhat/configs/pending-common/generic/CONFIG_NVME_TARGET_PASSTHRU diff --git a/redhat/configs/common/generic/CONFIG_NVME_TARGET_PASSTHRU b/redhat/configs/common/generic/CONFIG_NVME_TARGET_PASSTHRU new file mode 100644 index 000000000000..12bf02e23a41 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_NVME_TARGET_PASSTHRU @@ -0,0 +1 @@ +# CONFIG_NVME_TARGET_PASSTHRU is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_NVME_TARGET_PASSTHRU b/redhat/configs/pending-common/generic/CONFIG_NVME_TARGET_PASSTHRU deleted file mode 100644 index 2795e2bb3e5e..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_NVME_TARGET_PASSTHRU +++ /dev/null @@ -1,22 +0,0 @@ -# CONFIG_NVME_TARGET_PASSTHRU: -# -# This enables target side NVMe passthru controller support for the -# NVMe Over Fabrics protocol. It allows for hosts to manage and -# directly access an actual NVMe controller residing on the target -# side, incuding executing Vendor Unique Commands. -# -# If unsure, say N. -# -# Symbol: NVME_TARGET_PASSTHRU [=n] -# Type : bool -# Defined at drivers/nvme/target/Kconfig:19 -# Prompt: NVMe Target Passthrough support -# Depends on: NVME_TARGET [=m] && (NVME_CORE [=m]=y || NVME_CORE [=m]=NVME_TARGET [=m]) -# Location: -# -> Device Drivers -# -> NVME Support -# -> NVMe Target support (NVME_TARGET [=m]) -# -# -# -# CONFIG_NVME_TARGET_PASSTHRU is not set -- GitLab

5 4

[OS-BUILD PATCH] common: enable RTC_SYSTOHC to supplement update_persistent_clock64
by GitLab Bridge on behalf of pbrobinson 10 Mar '21

10 Mar '21

From: Peter Robinson <pbrobinson(a)gmail.com> We already enable RTC_HCTOSYS in common config, this is the inverse for syncing NTP to HW RTCs, and seems slightly better/preferred on non x86-style CMOS RTCa than update_persistent_clock. Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com> --- redhat/configs/common/generic/CONFIG_RTC_SYSTOHC | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/redhat/configs/common/generic/CONFIG_RTC_SYSTOHC b/redhat/configs/common/generic/CONFIG_RTC_SYSTOHC index 03ebe734a152..f3581c76b8c6 100644 --- a/redhat/configs/common/generic/CONFIG_RTC_SYSTOHC +++ b/redhat/configs/common/generic/CONFIG_RTC_SYSTOHC @@ -1 +1 @@ -# CONFIG_RTC_SYSTOHC is not set +CONFIG_RTC_SYSTOHC=y -- GitLab

2 3

[OS-BUILD PATCH] efi: The EFI_VARS is legacy and now x86 only
by GitLab Bridge on behalf of pbrobinson 10 Mar '21

10 Mar '21

From: Peter Robinson <pbrobinson(a)gmail.com> As of upstream commit 963fabf the EFI_VARS option is set to x86 only as it's long been deprecated pre !intel support and is due to be removed so it now does nothing on arm platforms. Fedora actually disabled this on x86 too, I do wonder if it's worth considering disabling it in ark platforms too? Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com> Cc: Mark Salter <msalter(a)redhat.com> Cc: Al Stone <ahs3(a)redhat.com> --- redhat/configs/ark/generic/arm/aarch64/CONFIG_EFI_VARS | 1 - redhat/configs/fedora/generic/arm/CONFIG_EFI_VARS | 1 - 2 files changed, 2 deletions(-) delete mode 100644 redhat/configs/ark/generic/arm/aarch64/CONFIG_EFI_VARS delete mode 100644 redhat/configs/fedora/generic/arm/CONFIG_EFI_VARS diff --git a/redhat/configs/ark/generic/arm/aarch64/CONFIG_EFI_VARS b/redhat/configs/ark/generic/arm/aarch64/CONFIG_EFI_VARS deleted file mode 100644 index b9206d9f457a..000000000000 --- a/redhat/configs/ark/generic/arm/aarch64/CONFIG_EFI_VARS +++ /dev/null @@ -1 +0,0 @@ -CONFIG_EFI_VARS=y diff --git a/redhat/configs/fedora/generic/arm/CONFIG_EFI_VARS b/redhat/configs/fedora/generic/arm/CONFIG_EFI_VARS deleted file mode 100644 index b9206d9f457a..000000000000 --- a/redhat/configs/fedora/generic/arm/CONFIG_EFI_VARS +++ /dev/null @@ -1 +0,0 @@ -CONFIG_EFI_VARS=y -- GitLab

6 6

[OS-BUILD PATCH] generic: arm: enable SCMI for all options
by GitLab Bridge on behalf of pbrobinson 10 Mar '21

10 Mar '21

From: Peter Robinson <pbrobinson(a)gmail.com> The Arm System Control and Management Interface (SCMI) specification is a new standard firmware interface for Arm devices from Arm. Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com> CC: ahs3(a)redhat.com --- redhat/configs/ark/generic/arm/aarch64/CONFIG_ARM_SCMI_PROTOCOL | 1 - .../{fedora => common}/generic/arm/CONFIG_ARM_SCMI_CPUFREQ | 0 .../{fedora => common}/generic/arm/CONFIG_ARM_SCMI_POWER_DOMAIN | 0 .../{fedora => common}/generic/arm/CONFIG_ARM_SCMI_PROTOCOL | 0 .../{fedora => common}/generic/arm/CONFIG_COMMON_CLK_SCMI | 0 redhat/configs/{fedora => common}/generic/arm/CONFIG_RESET_SCMI | 0 .../{fedora => common}/generic/arm/CONFIG_SENSORS_ARM_SCMI | 0 7 files changed, 1 deletion(-) delete mode 100644 redhat/configs/ark/generic/arm/aarch64/CONFIG_ARM_SCMI_PROTOCOL rename redhat/configs/{fedora => common}/generic/arm/CONFIG_ARM_SCMI_CPUFREQ (100%) rename redhat/configs/{fedora => common}/generic/arm/CONFIG_ARM_SCMI_POWER_DOMAIN (100%) rename redhat/configs/{fedora => common}/generic/arm/CONFIG_ARM_SCMI_PROTOCOL (100%) rename redhat/configs/{fedora => common}/generic/arm/CONFIG_COMMON_CLK_SCMI (100%) rename redhat/configs/{fedora => common}/generic/arm/CONFIG_RESET_SCMI (100%) rename redhat/configs/{fedora => common}/generic/arm/CONFIG_SENSORS_ARM_SCMI (100%) diff --git a/redhat/configs/ark/generic/arm/aarch64/CONFIG_ARM_SCMI_PROTOCOL b/redhat/configs/ark/generic/arm/aarch64/CONFIG_ARM_SCMI_PROTOCOL deleted file mode 100644 index 8e99d7695567..000000000000 --- a/redhat/configs/ark/generic/arm/aarch64/CONFIG_ARM_SCMI_PROTOCOL +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_ARM_SCMI_PROTOCOL is not set diff --git a/redhat/configs/fedora/generic/arm/CONFIG_ARM_SCMI_CPUFREQ b/redhat/configs/common/generic/arm/CONFIG_ARM_SCMI_CPUFREQ similarity index 100% rename from redhat/configs/fedora/generic/arm/CONFIG_ARM_SCMI_CPUFREQ rename to redhat/configs/common/generic/arm/CONFIG_ARM_SCMI_CPUFREQ diff --git a/redhat/configs/fedora/generic/arm/CONFIG_ARM_SCMI_POWER_DOMAIN b/redhat/configs/common/generic/arm/CONFIG_ARM_SCMI_POWER_DOMAIN similarity index 100% rename from redhat/configs/fedora/generic/arm/CONFIG_ARM_SCMI_POWER_DOMAIN rename to redhat/configs/common/generic/arm/CONFIG_ARM_SCMI_POWER_DOMAIN diff --git a/redhat/configs/fedora/generic/arm/CONFIG_ARM_SCMI_PROTOCOL b/redhat/configs/common/generic/arm/CONFIG_ARM_SCMI_PROTOCOL similarity index 100% rename from redhat/configs/fedora/generic/arm/CONFIG_ARM_SCMI_PROTOCOL rename to redhat/configs/common/generic/arm/CONFIG_ARM_SCMI_PROTOCOL diff --git a/redhat/configs/fedora/generic/arm/CONFIG_COMMON_CLK_SCMI b/redhat/configs/common/generic/arm/CONFIG_COMMON_CLK_SCMI similarity index 100% rename from redhat/configs/fedora/generic/arm/CONFIG_COMMON_CLK_SCMI rename to redhat/configs/common/generic/arm/CONFIG_COMMON_CLK_SCMI diff --git a/redhat/configs/fedora/generic/arm/CONFIG_RESET_SCMI b/redhat/configs/common/generic/arm/CONFIG_RESET_SCMI similarity index 100% rename from redhat/configs/fedora/generic/arm/CONFIG_RESET_SCMI rename to redhat/configs/common/generic/arm/CONFIG_RESET_SCMI diff --git a/redhat/configs/fedora/generic/arm/CONFIG_SENSORS_ARM_SCMI b/redhat/configs/common/generic/arm/CONFIG_SENSORS_ARM_SCMI similarity index 100% rename from redhat/configs/fedora/generic/arm/CONFIG_SENSORS_ARM_SCMI rename to redhat/configs/common/generic/arm/CONFIG_SENSORS_ARM_SCMI -- GitLab

4 4

[OS-BUILD PATCH] common: fix WM8804 codec dependencies
by GitLab Bridge on behalf of pbrobinson 09 Mar '21

09 Mar '21

From: Peter Robinson <pbrobinson(a)redhat.com> The WM8804 codec is required for Intel Apollo Lake support so enable it as it's a supported RHEL for Edge platform. Some minor cleanups for the WM8804 codec configs while we're at it. Signed-off-by: Peter Robinson <pbrobinson(a)redhat.com> --- .../generic/x86/CONFIG_SND_SOC_WM8804_I2C | 0 .../fedora/generic/CONFIG_SND_SOC_WM8804 | 1 - .../fedora/generic/arm/CONFIG_SND_SOC_WM8804 | 1 - .../x86/CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH | 23 ------------------- .../fedora/generic/x86/CONFIG_SND_SOC_WM8804 | 1 - 5 files changed, 26 deletions(-) rename redhat/configs/{fedora => common}/generic/x86/CONFIG_SND_SOC_WM8804_I2C (100%) delete mode 100644 redhat/configs/fedora/generic/CONFIG_SND_SOC_WM8804 delete mode 100644 redhat/configs/fedora/generic/arm/CONFIG_SND_SOC_WM8804 delete mode 100644 redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH delete mode 100644 redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_WM8804 diff --git a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_WM8804_I2C b/redhat/configs/common/generic/x86/CONFIG_SND_SOC_WM8804_I2C similarity index 100% rename from redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_WM8804_I2C rename to redhat/configs/common/generic/x86/CONFIG_SND_SOC_WM8804_I2C diff --git a/redhat/configs/fedora/generic/CONFIG_SND_SOC_WM8804 b/redhat/configs/fedora/generic/CONFIG_SND_SOC_WM8804 deleted file mode 100644 index 074702b5ef5e..000000000000 --- a/redhat/configs/fedora/generic/CONFIG_SND_SOC_WM8804 +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_SND_SOC_WM8804 is not set diff --git a/redhat/configs/fedora/generic/arm/CONFIG_SND_SOC_WM8804 b/redhat/configs/fedora/generic/arm/CONFIG_SND_SOC_WM8804 deleted file mode 100644 index 04b89d9ff78b..000000000000 --- a/redhat/configs/fedora/generic/arm/CONFIG_SND_SOC_WM8804 +++ /dev/null @@ -1 +0,0 @@ -CONFIG_SND_SOC_WM8804=m diff --git a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH deleted file mode 100644 index bb7ee45866a6..000000000000 --- a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH +++ /dev/null @@ -1,23 +0,0 @@ -# CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH: -# -# This adds support for ASoC machine driver for Intel platforms -# with the Wolfson/Cirrus WM8804 I2S audio codec. -# Say Y or m if you have such a device. This is a recommended option. -# If unsure select "N". -# -# Symbol: SND_SOC_INTEL_SOF_WM8804_MACH [=n] -# Type : tristate -# Defined at sound/soc/intel/boards/Kconfig:329 -# Prompt: SOF with Wolfson/Cirrus WM8804 codec -# Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_MACH [=y] && SND_SOC_SOF_APOLLOLAKE [=m] && I2C [=y] && ACPI [=y] && (MFD_INTEL_LPSS [=y] || COMPILE_TEST [=n]) -# Location: -# -> Device Drivers -# -> Sound card support (SOUND [=m]) -# -> Advanced Linux Sound Architecture (SND [=m]) -# -> ALSA for SoC audio support (SND_SOC [=m]) -# -> Intel Machine drivers (SND_SOC_INTEL_MACH [=y]) -# Selects: SND_SOC_WM8804_I2C [=n] -# -# -# -CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH=m diff --git a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_WM8804 b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_WM8804 deleted file mode 100644 index 04b89d9ff78b..000000000000 --- a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_WM8804 +++ /dev/null @@ -1 +0,0 @@ -CONFIG_SND_SOC_WM8804=m -- GitLab

6 5

[OS-BUILD PATCH 0/7] Move all x86 legacy input options to that architecture
by GitLab Bridge on behalf of pbrobinson 09 Mar '21

09 Mar '21

From: pbrobinson on gitlab.com None of the non x86 architectures support PS2, AT keyboards, i8042 controllers and related bits. This cleans up a bunch of those options as well as syncing some of the Fedora options on non x86 to be the same as ARK by moving the ARK bits to generic. Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com>

5 16

[OS-BUILD PATCH] Disable bluetooth highspeed by default
by GitLab Bridge on behalf of pbrobinson 09 Mar '21

09 Mar '21

From: Peter Robinson <pbrobinson(a)gmail.com> Upstream has disabled BT_HS by disabled because it wasn't widely adopted. It's also been referenced upstream by BleedingTooth vulnerability: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-0… Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com> --- redhat/configs/common/generic/CONFIG_BT_HS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/redhat/configs/common/generic/CONFIG_BT_HS b/redhat/configs/common/generic/CONFIG_BT_HS index e0151a2e9e0d..fbbd6bcf002f 100644 --- a/redhat/configs/common/generic/CONFIG_BT_HS +++ b/redhat/configs/common/generic/CONFIG_BT_HS @@ -1 +1 @@ -CONFIG_BT_HS=y +# CONFIG_BT_HS is not set -- GitLab

4 3

[OS-BUILD PATCH 0/8] 5.11 general can cleanup
by GitLab Bridge on behalf of pbrobinson 08 Mar '21

08 Mar '21

From: pbrobinson on gitlab.com Cleanups to CAN for the enabled core CAN support and devices across common/ark/fedora. Signed-off-by: Peter Robinson <pbrobinson(a)redhat.com>

4 11

[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.debug
by CKI Gitlab (via Email Bridge) 05 Mar '21

05 Mar '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in lib/Kconfig.debug Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_DEBUG_IRQFLAGS: Enables checks for potentially unsafe enabling or disabling of interrupts, such as calling raw_local_irq_restore() when interrupts are enabled. Symbol: DEBUG_IRQFLAGS [=n] Type : bool Defined at lib/Kconfig.debug:1427 Prompt: Debug IRQ flag manipulation Location: -> Kernel hacking Selected by [n]: - DEBUG_LOCKDEP [=n] && DEBUG_KERNEL [=y] && LOCKDEP [=n] --- Cc: Prarit Bhargava <prarit(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_DEBUG_IRQFLAGS b/redhat/configs/common/generic/CONFIG_DEBUG_IRQFLAGS --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_DEBUG_IRQFLAGS @@ -0,0 +1 @@ +# CONFIG_DEBUG_IRQFLAGS is not set diff a/redhat/configs/pending-common/generic/CONFIG_DEBUG_IRQFLAGS b/redhat/configs/pending-common/generic/CONFIG_DEBUG_IRQFLAGS --- a/redhat/configs/pending-common/generic/CONFIG_DEBUG_IRQFLAGS +++ /dev/null @@ -1,18 +0,0 @@ -# CONFIG_DEBUG_IRQFLAGS: -# -# Enables checks for potentially unsafe enabling or disabling of -# interrupts, such as calling raw_local_irq_restore() when interrupts -# are enabled. -# -# Symbol: DEBUG_IRQFLAGS [=n] -# Type : bool -# Defined at lib/Kconfig.debug:1427 -# Prompt: Debug IRQ flag manipulation -# Location: -# -> Kernel hacking -# Selected by [n]: -# - DEBUG_LOCKDEP [=n] && DEBUG_KERNEL [=y] && LOCKDEP [=n] -# -# -# -# CONFIG_DEBUG_IRQFLAGS is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/912

3 2

Re: Building custom kernels
by Julian Sikorski 02 Mar '21

02 Mar '21

W dniu 27.02.2021 o 20:59, Julian Sikorski pisze: > Hi, > > I am trying to test some Renoir s2idle patches [1]. It appears that > Fedora kernel source is now maintained on gitlab as kernel-ark [2]. What > I tried is adding the patches to the fedora-5.11 branch and running make > dist-srpm, but it failed due to config mismatch on CONFIG_INIT_STACK_NONE: > > Processing > /home/julas/cvs/fedora/kernel-ark/redhat/configs/kernel-aarch64-fedora.config > ... Error: Mismatches found in configuration files > Found CONFIG_INIT_STACK_NONE=y after generation, had > CONFIG_INIT_STACK_NONE=is not set in Source tree > make[1]: *** [Makefile:145: dist-configs-check] Błąd 1 > > Is this expected? Is there a better way of testing patches on Fedora > kernels? Thanks for the help in advance. > > Best regards, > Julian > > [1] https://gitlab.freedesktop.org/drm/amd/-/issues/1230 > [2] https://gitlab.com/cki-project/kernel-ark Hi, the same keeps happening if I try to merge os-build into agdf5 tree or even if I try to make srpm in the ark-latest branch. Is this normal? Best regards, Julian

2 2

[OS-BUILD PATCH 0/4] Drop stale pinephone patches
by Herton Krzesinski (via Email Bridge) 01 Mar '21

01 Mar '21

From: Herton Krzesinski on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/925 Seems a while ago PinePhone patches not yet upstreamed where added. However, some of them were reworked/dropped in its way upstream, and this looks the final version that went in: https://patchwork.freedesktop.org/series/79025/ It got merged upstream through these commits: 5f5df8b4253f12dbc0b9e328b3334ce28c16fc08^..c8a753484066a6382d2539d3dca14 28164a682bf a6a22f82c90dab8966fc07bd7e798a0680803995^..60f2de5ffbf0ed7c0d9789bcc1968 84427e8cff5 However, we still have some stale commits/patches that were not dropped with the upstream merge. Remove them now.

5 13

Dealing with i915 graphics issues reported by multipe people in kernel >= 5.10.9
by Hans de Goede 01 Mar '21

01 Mar '21

Hi, I've been working with various reporters to try and get the sometimes severe gfx glitches which people are seeing with kernel >= 5.10.9 resolved, see the following bugs: 1843274 - i915 GPU Hang with kernel 5.7 on Haswell (Acer C720P Chromebook) 1925346 - Screen glitches after updating to Kernel 5.10.10 1925903 - Flickering UI elements, screen instability (Wayland) 1931065 - Frequent i915 hangs I've written 2 patches 2 address this and asked users to test Fedora-kernel scratch-builds with those patches added. The first patch is i915-revert.patch, this reverts 3 troublesome commits which were first added in 5.10.9 these commit change the i915 mitigations for a year old i915 CVE which IIRC was mostly about data leaking from a previous GPU context to the next. These patches enable these mitigations on more GPU models, where they were previously disabled because they were causing issues... Reporters have reported a 100% success-rate in getting rid of the gfx issues with these 3 reverts. The second patch is i915-fixes.patch, this cherry-picks 3 patches from -next instead (these were suggested by i915 upstream) and this also helps for most users, but some users still report some rendering artifacts (but overall things are much better). Upstream has gone silent on the issue of there still being rendering artifacts with the 3 cherry-picked fixes unfortunately. Given that we are getting more and more bug-reports about this I think that we should be do something about this downstream. Upstream seams to be aiming for fixing things, rather then reverting, so going with i915-fixes.patch will stay the closest to what I expect to land in 5.10.y and 5.11.y at some point. Regards, Hans

3 9

[OS-BUILD PATCH] [redhat] New configs in arch/powerpc
by GitLab Bridge on behalf of jeremycline 27 Feb '21

27 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_CMDLINE: On some platforms, there is currently no way for the boot loader to pass arguments to the kernel. For these platforms, you can supply some command-line options at build time by entering them here. In most cases you will need to specify the root device here. Symbol: CMDLINE [=] Type : string Defined at arch/powerpc/Kconfig:882 Prompt: Initial kernel command string Location: -> Kernel options --- CONFIG_PPC_QUEUED_SPINLOCKS: Say Y here to use queued spinlocks which give better scalability and fairness on large SMP and NUMA systems without harming single threaded performance. This option is currently experimental, the code is more complex and less tested so it defaults to "N" for the moment. If unsure, say "N". Symbol: PPC_QUEUED_SPINLOCKS [=n] Type : bool Defined at arch/powerpc/Kconfig:497 Prompt: Queued spinlocks Depends on: SMP [=y] Location: -> Kernel options --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/common/generic/CONFIG_CMDLINE | 1 + .../generic/CONFIG_PPC_QUEUED_SPINLOCKS | 1 + .../pending-common/generic/CONFIG_CMDLINE | 17 -------------- .../generic/CONFIG_PPC_QUEUED_SPINLOCKS | 22 ------------------- 4 files changed, 2 insertions(+), 39 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_CMDLINE create mode 100644 redhat/configs/common/generic/CONFIG_PPC_QUEUED_SPINLOCKS delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CMDLINE delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PPC_QUEUED_SPINLOCKS diff --git a/redhat/configs/common/generic/CONFIG_CMDLINE b/redhat/configs/common/generic/CONFIG_CMDLINE new file mode 100644 index 000000000000..f3083e1e5200 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_CMDLINE @@ -0,0 +1 @@ +CONFIG_CMDLINE="" diff --git a/redhat/configs/common/generic/CONFIG_PPC_QUEUED_SPINLOCKS b/redhat/configs/common/generic/CONFIG_PPC_QUEUED_SPINLOCKS new file mode 100644 index 000000000000..f1f7e79da5c3 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_PPC_QUEUED_SPINLOCKS @@ -0,0 +1 @@ +# CONFIG_PPC_QUEUED_SPINLOCKS is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_CMDLINE b/redhat/configs/pending-common/generic/CONFIG_CMDLINE deleted file mode 100644 index 10611732c5eb..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_CMDLINE +++ /dev/null @@ -1,17 +0,0 @@ -# CONFIG_CMDLINE: -# -# On some platforms, there is currently no way for the boot loader to -# pass arguments to the kernel. For these platforms, you can supply -# some command-line options at build time by entering them here. In -# most cases you will need to specify the root device here. -# -# Symbol: CMDLINE [=] -# Type : string -# Defined at arch/powerpc/Kconfig:882 -# Prompt: Initial kernel command string -# Location: -# -> Kernel options -# -# -# -CONFIG_CMDLINE="" diff --git a/redhat/configs/pending-common/generic/CONFIG_PPC_QUEUED_SPINLOCKS b/redhat/configs/pending-common/generic/CONFIG_PPC_QUEUED_SPINLOCKS deleted file mode 100644 index 90ecdc77e696..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_PPC_QUEUED_SPINLOCKS +++ /dev/null @@ -1,22 +0,0 @@ -# CONFIG_PPC_QUEUED_SPINLOCKS: -# -# Say Y here to use queued spinlocks which give better scalability and -# fairness on large SMP and NUMA systems without harming single threaded -# performance. -# -# This option is currently experimental, the code is more complex and -# less tested so it defaults to "N" for the moment. -# -# If unsure, say "N". -# -# Symbol: PPC_QUEUED_SPINLOCKS [=n] -# Type : bool -# Defined at arch/powerpc/Kconfig:497 -# Prompt: Queued spinlocks -# Depends on: SMP [=y] -# Location: -# -> Kernel options -# -# -# -# CONFIG_PPC_QUEUED_SPINLOCKS is not set -- GitLab

4 7

✅ PASS: Test report for kernel 5.10.19-200.fc33 (fedora-33)
by CKI Project 27 Feb '21

27 Feb '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.10.19-200.fc33 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=62729118 The results of these automated tests are provided below. Overall result: PASSED Tests: OK All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ Storage blktests 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage nvme - tcp 🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ stress: stress-ng ppc64le: Host 1: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ LTP ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) 🚧 ⚡⚡⚡ CIFS Connectathon 🚧 ⚡⚡⚡ Ethernet drivers sanity Host 2: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test ⚡⚡⚡ LTP ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) 🚧 ⚡⚡⚡ CIFS Connectathon 🚧 ⚡⚡⚡ Ethernet drivers sanity s390x: Host 1: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test 🚧 ✅ Storage blktests 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ stress: stress-ng x86_64: Host 1: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test ✅ ACPI table test ⚡⚡⚡ LTP ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) 🚧 ⚡⚡⚡ CIFS Connectathon 🚧 ⚡⚡⚡ Ethernet drivers sanity Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

A linux-5.11.1.tar.xz that actually contains 5.11 instead of 5.11.1?
by Thorsten Leemhuis 26 Feb '21

26 Feb '21

Lo! The new stable workflow based on kernel-ark confuses me and I want to ask for advice if I got something wrong or if things are really as they appear to me: The sources file in dist.git for the Fedora 34 kernel currently(¹) refers to a file that is called linux-5.11.1.tar.xz – but if you download ("fedpkg sources") and unpack that file and look closer, you'll notice that it actually contains the sources from Linux 5.11 (and not 5.11.1). Is that intentional or just an mistake that someone did somewhere? Because I find that really confusing. Once I looked closer I noticed that the diff from Linux 5.11 -> 5.11.1 can actually be found in the file patch-5.11.1-redhat.patch ( https://src.fedoraproject.org/rpms/kernel/blob/f34/f/patch-5.11.1-redhat.pa… ) - entangled with Fedora specific patches. I didn't try, but I'm therefore pretty sure that rebuilding the kernel SRPM using "--with-vanilla" (for details see https://src.fedoraproject.org/rpms/kernel/blob/f34/f/kernel.spec ) will lead to unexpected results (I guess you will get a kernel that partly thinks it's 5.11.1, but in truth is 5.11; if that acutally boot I suspect users won't be able to spot this). Are things really as described above or did I get something wrong? Because it looks utterly confusing to me. I have some issues with the whole kernel-ark workflow for a while now and hence for a few week already considered asking on the Fedora packaging list (the Fedora Packaging Committe's list) for advice if kernel.spec violates the packaging guidelines too much (a complex package like the kernel likely will always have some issues). I guess this will finally make me do that, but before going down that route I wanted to check here if I got something wrong. CU, knurd (¹) as of https://src.fedoraproject.org/rpms/kernel/c/07992209452cd7ba529ffdbdd83d01d…

2 3

Re: Dealing with i915 graphics issues reported by multipe people in kernel >= 5.10.9
by Hans de Goede 24 Feb '21

24 Feb '21

Hi, On 2/24/21 6:32 AM, Thorsten Leemhuis wrote: > Hi! > > On 23.02.21 18:25, Hans de Goede wrote: >> >> I've been working with various reporters to try and get the sometimes severe >> gfx glitches which people are seeing with kernel >= 5.10.9 resolved, see the >> following bugs: >> >> 1843274 - i915 GPU Hang with kernel 5.7 on Haswell (Acer C720P Chromebook) >> 1925346 - Screen glitches after updating to Kernel 5.10.10 >> 1925903 - Flickering UI elements, screen instability (Wayland) >> 1931065 - Frequent i915 hangs >> >> I've written 2 patches 2 address this and asked users to test Fedora-kernel >> scratch-builds with those patches added. > > Thx for working on this, I have a friend that is affected by this. > >> […] > >> Reporters have reported a 100% success-rate in getting rid of the gfx >> issues with these 3 reverts. >> […] Upstream has gone silent on the issue of there still being rendering > artifacts with the 3 cherry-picked fixes unfortunately. >> >> Given that we are getting more and more bug-reports about this I think >> that we should be do something about this downstream. Upstream seams >> to be aiming for fixing things, rather then reverting, so going with >> i915-fixes.patch will stay the closest to what I expect to land in >> 5.10.y and 5.11.y at some point. > > Out of curiosity: Upstream means "the drm/i915 folks here"? Yes. > What about GregKH? Is he aware of this? Yes, Greg is aware of this (I Cc-ed him on my initial bug report to the i915 folks and he has replied in the upstream thread about this) > He's not Linus, but he hates regressions nearly as much afaics, so why not maybe he is willing to revert those patches quickly and thus maybe force the drm/i915 folks into action? The i915 folks have acted on this, hence the patch with 3 cherry-picked fixes from -next. This patch seems to work well for most reporters, there is a single reporter who is still seeing issues with the 3 cherry-picked fixes. I plan to ping Greg about merging the 3 fixes from -next, assuming that they have landed in Linus' tree by now (I have not pinged Greg yet, because first I need to check that the 3 fixes have indeed landed). Regards, Hans

1 0

✅ PASS: Test report for kernel 5.10.18-200.fc33 (fedora-33)
by CKI Project 24 Feb '21

24 Feb '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.10.18-200.fc33 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=62602244 The results of these automated tests are provided below. Overall result: PASSED Tests: OK All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng ppc64le: Host 1: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test 🚧 ⚡⚡⚡ xfstests - ext4 🚧 ⚡⚡⚡ xfstests - xfs 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ Storage blktests 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage nvme - tcp 🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test Host 3: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test s390x: Host 1: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test 🚧 ✅ Storage blktests 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng x86_64: Host 1: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ xfstests - nfsv4.2 🚧 ✅ xfstests - cifsv3.11 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

[OS-BUILD PATCH] [redhat] New configs in drivers/hwmon
by CKI Gitlab (via Email Bridge) 23 Feb '21

23 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/hwmon Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_SENSORS_AHT10: If you say yes here, you get support for the Aosong AHT10 temperature and humidity sensors This driver can also be built as a module. If so, the module will be called aht10. Symbol: SENSORS_AHT10 [=n] Type : tristate Defined at drivers/hwmon/Kconfig:247 Prompt: Aosong AHT10 Depends on: HWMON [=y] && I2C [=y] Location: -> Device Drivers -> Hardware Monitoring support (HWMON [=y]) --- CONFIG_SENSORS_TPS23861: If you say yes here you get support for Texas Instruments TPS23861 802.3at PoE PSE chips. This driver can also be built as a module. If so, the module will be called tps23861. Symbol: SENSORS_TPS23861 [=n] Type : tristate Defined at drivers/hwmon/Kconfig:1136 Prompt: Texas Instruments TPS23861 PoE PSE Depends on: HWMON [=y] && I2C [=y] Location: -> Device Drivers -> Hardware Monitoring support (HWMON [=y]) Selects: REGMAP_I2C [=m] --- Cc: Dean Nelson <dnelson(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_SENSORS_AHT10 b/redhat/configs/common/generic/CONFIG_SENSORS_AHT10 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_SENSORS_AHT10 @@ -0,0 +1 @@ +# CONFIG_SENSORS_AHT10 is not set diff a/redhat/configs/common/generic/CONFIG_SENSORS_TPS23861 b/redhat/configs/common/generic/CONFIG_SENSORS_TPS23861 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_SENSORS_TPS23861 @@ -0,0 +1 @@ +# CONFIG_SENSORS_TPS23861 is not set diff a/redhat/configs/pending-common/generic/CONFIG_SENSORS_AHT10 b/redhat/configs/pending-common/generic/CONFIG_SENSORS_AHT10 --- a/redhat/configs/pending-common/generic/CONFIG_SENSORS_AHT10 +++ /dev/null @@ -1,20 +0,0 @@ -# CONFIG_SENSORS_AHT10: -# -# If you say yes here, you get support for the Aosong AHT10 -# temperature and humidity sensors -# -# This driver can also be built as a module. If so, the module -# will be called aht10. -# -# Symbol: SENSORS_AHT10 [=n] -# Type : tristate -# Defined at drivers/hwmon/Kconfig:247 -# Prompt: Aosong AHT10 -# Depends on: HWMON [=y] && I2C [=y] -# Location: -# -> Device Drivers -# -> Hardware Monitoring support (HWMON [=y]) -# -# -# -# CONFIG_SENSORS_AHT10 is not set diff a/redhat/configs/pending-common/generic/CONFIG_SENSORS_TPS23861 b/redhat/configs/pending-common/generic/CONFIG_SENSORS_TPS23861 --- a/redhat/configs/pending-common/generic/CONFIG_SENSORS_TPS23861 +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_SENSORS_TPS23861: -# -# If you say yes here you get support for Texas Instruments -# TPS23861 802.3at PoE PSE chips. -# -# This driver can also be built as a module. If so, the module -# will be called tps23861. -# -# Symbol: SENSORS_TPS23861 [=n] -# Type : tristate -# Defined at drivers/hwmon/Kconfig:1136 -# Prompt: Texas Instruments TPS23861 PoE PSE -# Depends on: HWMON [=y] && I2C [=y] -# Location: -# -> Device Drivers -# -> Hardware Monitoring support (HWMON [=y]) -# Selects: REGMAP_I2C [=m] -# -# -# -# CONFIG_SENSORS_TPS23861 is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/916

2 1

[OS-BUILD PATCH] [redhat] New configs in drivers/clk
by CKI Gitlab (via Email Bridge) 23 Feb '21

23 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/clk Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_COMMON_CLK_AXI_CLKGEN: Support for the Analog Devices axi-clkgen pcore clock generator for Xilinx FPGAs. It is commonly used in Analog Devices' reference designs. Symbol: COMMON_CLK_AXI_CLKGEN [=n] Type : tristate Defined at drivers/clk/Kconfig:248 Prompt: AXI clkgen driver Depends on: COMMON_CLK [=y] && (HAS_IOMEM [=y] || COMPILE_TEST [=n]) && OF [=y] Location: -> Device Drivers -> Common Clock Framework (COMMON_CLK [=y]) --- Cc: Mark Salter <msalter(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_COMMON_CLK_AXI_CLKGEN b/redhat/configs/common/generic/CONFIG_COMMON_CLK_AXI_CLKGEN --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_COMMON_CLK_AXI_CLKGEN @@ -0,0 +1 @@ +# CONFIG_COMMON_CLK_AXI_CLKGEN is not set diff a/redhat/configs/pending-common/generic/CONFIG_COMMON_CLK_AXI_CLKGEN b/redhat/configs/pending-common/generic/CONFIG_COMMON_CLK_AXI_CLKGEN --- a/redhat/configs/pending-common/generic/CONFIG_COMMON_CLK_AXI_CLKGEN +++ /dev/null @@ -1,17 +0,0 @@ -# CONFIG_COMMON_CLK_AXI_CLKGEN: -# -# Support for the Analog Devices axi-clkgen pcore clock generator for Xilinx -# FPGAs. It is commonly used in Analog Devices' reference designs. -# -# Symbol: COMMON_CLK_AXI_CLKGEN [=n] -# Type : tristate -# Defined at drivers/clk/Kconfig:248 -# Prompt: AXI clkgen driver -# Depends on: COMMON_CLK [=y] && (HAS_IOMEM [=y] || COMPILE_TEST [=n]) && OF [=y] -# Location: -# -> Device Drivers -# -> Common Clock Framework (COMMON_CLK [=y]) -# -# -# -# CONFIG_COMMON_CLK_AXI_CLKGEN is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/915

2 1

Fwd: [PATCHv2] media/rc: compile rc-cec.c into rc-core
by Hans de Goede 23 Feb '21

23 Feb '21

Hi, I've been discussing this https://retrace.fedoraproject.org/faf/problems/8150/ ABRT reported kernel backtrace with upstream, because it is seeing about 200,000 traces being reported per 14 days (its number 2 in the top ten). The attached patch was just posted upstream and this should fix this. It is also available here: https://lore.kernel.org/linux-media/20210223121246.GA8647@gofer.mess.org/ I think we should consider adding this as a downstream patch for now, to reduce the number of reports which we are getting about this. Regards, Hans

1 0

[OS-BUILD PATCH] [redhat] New configs in drivers/scsi
by CKI Gitlab (via Email Bridge) 23 Feb '21

23 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/scsi Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE: Set Y to default enable DEBUGFS for SCSI_HISI_SAS Symbol: SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE [=n] Type : bool Defined at drivers/scsi/hisi_sas/Kconfig:22 Prompt: HiSilicon SAS debugging default enable Depends on: SCSI_LOWLEVEL [=y] && SCSI [=y] && SCSI_HISI_SAS [=m] Location: -> Device Drivers -> SCSI device support -> SCSI low-level drivers (SCSI_LOWLEVEL [=y]) -> HiSilicon SAS (SCSI_HISI_SAS [=m]) --- Cc: "Ewan D. Milne" <emilne(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE b/redhat/configs/common/generic/CONFIG_SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE @@ -0,0 +1 @@ +# CONFIG_SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE is not set diff a/redhat/configs/pending-common/generic/CONFIG_SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE b/redhat/configs/pending-common/generic/CONFIG_SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE --- a/redhat/configs/pending-common/generic/CONFIG_SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE +++ /dev/null @@ -1,18 +0,0 @@ -# CONFIG_SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE: -# -# Set Y to default enable DEBUGFS for SCSI_HISI_SAS -# -# Symbol: SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE [=n] -# Type : bool -# Defined at drivers/scsi/hisi_sas/Kconfig:22 -# Prompt: HiSilicon SAS debugging default enable -# Depends on: SCSI_LOWLEVEL [=y] && SCSI [=y] && SCSI_HISI_SAS [=m] -# Location: -# -> Device Drivers -# -> SCSI device support -# -> SCSI low-level drivers (SCSI_LOWLEVEL [=y]) -# -> HiSilicon SAS (SCSI_HISI_SAS [=m]) -# -# -# -# CONFIG_SCSI_HISI_SAS_DEBUGFS_DEFAULT_ENABLE is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/920

1 0

[OS-BUILD PATCHv3] [redhat] New configs in drivers/net/ethernet/mellanox
by CKI Gitlab (via Email Bridge) 23 Feb '21

23 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/net/ethernet/mellanox Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_MLX5_SF: Build support for subfuction device in the NIC. A Mellanox subfunction device can support RDMA, netdevice and vdpa device. It is similar to a SRIOV VF but it doesn't require SRIOV support. Symbol: MLX5_SF [=n] Type : bool Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:205 Prompt: Mellanox Technologies subfunction device support using auxiliary device Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_CORE [=m] && MLX5_CORE_EN [=y] Location: -> Device Drivers -> Network device support (NETDEVICES [=y]) -> Ethernet driver support (ETHERNET [=y]) -> Mellanox devices (NET_VENDOR_MELLANOX [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_MLX5_SF b/redhat/configs/common/generic/CONFIG_MLX5_SF --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_MLX5_SF @@ -0,0 +1 @@ +CONFIG_MLX5_SF=y diff a/redhat/configs/pending-common/generic/CONFIG_MLX5_SF b/redhat/configs/pending-common/generic/CONFIG_MLX5_SF --- a/redhat/configs/pending-common/generic/CONFIG_MLX5_SF +++ /dev/null @@ -1,20 +0,0 @@ -# CONFIG_MLX5_SF: -# -# Build support for subfuction device in the NIC. A Mellanox subfunction -# device can support RDMA, netdevice and vdpa device. -# It is similar to a SRIOV VF but it doesn't require SRIOV support. -# -# Symbol: MLX5_SF [=n] -# Type : bool -# Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:205 -# Prompt: Mellanox Technologies subfunction device support using auxiliary device -# Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_CORE [=m] && MLX5_CORE_EN [=y] -# Location: -# -> Device Drivers -# -> Network device support (NETDEVICES [=y]) -# -> Ethernet driver support (ETHERNET [=y]) -# -> Mellanox devices (NET_VENDOR_MELLANOX [=y]) -# -# -# -# CONFIG_MLX5_SF is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/908

2 2

[OS-BUILD PATCHv2] [redhat] New configs in drivers/net/ethernet/mellanox
by CKI Gitlab (via Email Bridge) 23 Feb '21

23 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/net/ethernet/mellanox Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_MLX5_SF: Build support for subfuction device in the NIC. A Mellanox subfunction device can support RDMA, netdevice and vdpa device. It is similar to a SRIOV VF but it doesn't require SRIOV support. Symbol: MLX5_SF [=n] Type : bool Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:205 Prompt: Mellanox Technologies subfunction device support using auxiliary device Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_CORE [=m] && MLX5_CORE_EN [=y] Location: -> Device Drivers -> Network device support (NETDEVICES [=y]) -> Ethernet driver support (ETHERNET [=y]) -> Mellanox devices (NET_VENDOR_MELLANOX [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_MLX5_SF b/redhat/configs/common/generic/CONFIG_MLX5_SF --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_MLX5_SF @@ -0,0 +1 @@ +# CONFIG_MLX5_SF is not set diff a/redhat/configs/pending-common/generic/CONFIG_MLX5_SF b/redhat/configs/pending-common/generic/CONFIG_MLX5_SF --- a/redhat/configs/pending-common/generic/CONFIG_MLX5_SF +++ /dev/null @@ -1,20 +0,0 @@ -# CONFIG_MLX5_SF: -# -# Build support for subfuction device in the NIC. A Mellanox subfunction -# device can support RDMA, netdevice and vdpa device. -# It is similar to a SRIOV VF but it doesn't require SRIOV support. -# -# Symbol: MLX5_SF [=n] -# Type : bool -# Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:205 -# Prompt: Mellanox Technologies subfunction device support using auxiliary device -# Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_CORE [=m] && MLX5_CORE_EN [=y] -# Location: -# -> Device Drivers -# -> Network device support (NETDEVICES [=y]) -# -> Ethernet driver support (ETHERNET [=y]) -# -> Mellanox devices (NET_VENDOR_MELLANOX [=y]) -# -# -# -# CONFIG_MLX5_SF is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/908

2 3

[OS-BUILD PATCHv2 0/2] [redhat] New configs in sound/core
by CKI Gitlab (via Email Bridge) 23 Feb '21

23 Feb '21

From: CKI Gitlab on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/914 Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_SND_JACK_INJECTION_DEBUG: This option can be used to enable or disable sound jack software injection. Say Y if you are debugging via jack injection interface. If unsure select "N". Symbol: SND_JACK_INJECTION_DEBUG [=n] Type : bool Defined at sound/core/Kconfig:190 Prompt: Sound jack injection interface via debugfs Depends on: SOUND [=m] && !UML && SND [=m] && SND_JACK [=y] && SND_DEBUG [=y] && DEBUG_FS [=y] Location: -> Device Drivers -> Sound card support (SOUND [=m]) -> Advanced Linux Sound Architecture (SND [=m]) -> Debug (SND_DEBUG [=y]) --- Cc: Jaroslav Kysela <jkysela(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>

2 4

[OS-BUILD PATCHv4 0/2] [redhat] New configs in drivers/perf
by CKI Gitlab (via Email Bridge) 23 Feb '21

23 Feb '21

From: CKI Gitlab on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/797 Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_ARM_DMC620_PMU: Support for PMU events monitoring on the ARM DMC-620 memory controller. Symbol: ARM_DMC620_PMU [=n] Type : tristate Defined at drivers/perf/Kconfig:133 Prompt: Enable PMU support for the ARM DMC-620 memory controller Depends on: PERF_EVENTS [=y] && (ARM64 [=y] && ACPI [=y] || COMPILE_TEST [=n]) Location: -> Device Drivers -> Performance monitor support --- Cc: Mark Salter <msalter(a)redhat.com> Cc: Mark Langsdorf <mlangsdo(a)redhat.com> Cc: Jeremy Linton <jlinton(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>

2 3

[OS-BUILD PATCHv3 0/2] [redhat] New configs in drivers/perf
by CKI Gitlab (via Email Bridge) 23 Feb '21

23 Feb '21

From: CKI Gitlab on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/797 Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_ARM_DMC620_PMU: Support for PMU events monitoring on the ARM DMC-620 memory controller. Symbol: ARM_DMC620_PMU [=n] Type : tristate Defined at drivers/perf/Kconfig:133 Prompt: Enable PMU support for the ARM DMC-620 memory controller Depends on: PERF_EVENTS [=y] && (ARM64 [=y] && ACPI [=y] || COMPILE_TEST [=n]) Location: -> Device Drivers -> Performance monitor support --- Cc: Mark Salter <msalter(a)redhat.com> Cc: Mark Langsdorf <mlangsdo(a)redhat.com> Cc: Jeremy Linton <jlinton(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>

1 2

[OS-BUILD PATCHv2] [redhat] New configs in arch/arm64
by CKI Gitlab (via Email Bridge) 23 Feb '21

23 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in arch/arm64 Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_ARCH_N5X: This enables support for Intel's eASIC N5X SoCFPGA Family. Symbol: ARCH_N5X [=n] Type : bool Defined at arch/arm64/Kconfig.platforms:16 Prompt: Intel's eASIC N5X SoCFPGA Family Location: -> Platform selection --- Cc: Mark Salter <msalter(a)redhat.com> Cc: Mark Langsdorf <mlangsdo(a)redhat.com> Cc: Jeremy Linton <jlinton(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/arm/aarch64/CONFIG_ARCH_N5X b/redhat/configs/common/generic/arm/aarch64/CONFIG_ARCH_N5X --- /dev/null +++ b/redhat/configs/common/generic/arm/aarch64/CONFIG_ARCH_N5X @@ -0,0 +1 @@ +# CONFIG_ARCH_N5X is not set diff a/redhat/configs/pending-common/generic/CONFIG_ARCH_N5X b/redhat/configs/pending-common/generic/CONFIG_ARCH_N5X --- a/redhat/configs/pending-common/generic/CONFIG_ARCH_N5X +++ /dev/null @@ -1,14 +0,0 @@ -# CONFIG_ARCH_N5X: -# -# This enables support for Intel's eASIC N5X SoCFPGA Family. -# -# Symbol: ARCH_N5X [=n] -# Type : bool -# Defined at arch/arm64/Kconfig.platforms:16 -# Prompt: Intel's eASIC N5X SoCFPGA Family -# Location: -# -> Platform selection -# -# -# -# CONFIG_ARCH_N5X is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/899

2 1

[OS-BUILD PATCHv2] [redhat] New configs in drivers/powercap
by CKI Gitlab (via Email Bridge) 23 Feb '21

23 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/powercap Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_DTPM: This enables support for the power capping for the dynamic thermal power management userspace engine. Symbol: DTPM [=n] Type : bool Defined at drivers/powercap/Kconfig:47 Prompt: Power capping for Dynamic Thermal Power Management Depends on: POWERCAP [=y] Location: -> Device Drivers -> Generic powercap sysfs driver (POWERCAP [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_DTPM b/redhat/configs/common/generic/CONFIG_DTPM --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_DTPM @@ -0,0 +1 @@ +# CONFIG_DTPM is not set diff a/redhat/configs/pending-common/generic/CONFIG_DTPM b/redhat/configs/pending-common/generic/CONFIG_DTPM --- a/redhat/configs/pending-common/generic/CONFIG_DTPM +++ /dev/null @@ -1,17 +0,0 @@ -# CONFIG_DTPM: -# -# This enables support for the power capping for the dynamic -# thermal power management userspace engine. -# -# Symbol: DTPM [=n] -# Type : bool -# Defined at drivers/powercap/Kconfig:47 -# Prompt: Power capping for Dynamic Thermal Power Management -# Depends on: POWERCAP [=y] -# Location: -# -> Device Drivers -# -> Generic powercap sysfs driver (POWERCAP [=y]) -# -# -# -# CONFIG_DTPM is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/910

1 0

[OS-BUILD PATCHv2 0/2] [redhat] New configs in drivers/perf
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: CKI Gitlab on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/797 Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_ARM_DMC620_PMU: Support for PMU events monitoring on the ARM DMC-620 memory controller. Symbol: ARM_DMC620_PMU [=n] Type : tristate Defined at drivers/perf/Kconfig:133 Prompt: Enable PMU support for the ARM DMC-620 memory controller Depends on: PERF_EVENTS [=y] && (ARM64 [=y] && ACPI [=y] || COMPILE_TEST [=n]) Location: -> Device Drivers -> Performance monitor support --- Cc: Mark Salter <msalter(a)redhat.com> Cc: Mark Langsdorf <mlangsdo(a)redhat.com> Cc: Jeremy Linton <jlinton(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>

3 4

[OS-BUILD PATCH] [redhat] New configs in arch/arm64
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in arch/arm64 Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_ARCH_N5X: This enables support for Intel's eASIC N5X SoCFPGA Family. Symbol: ARCH_N5X [=n] Type : bool Defined at arch/arm64/Kconfig.platforms:16 Prompt: Intel's eASIC N5X SoCFPGA Family Location: -> Platform selection --- Cc: Mark Salter <msalter(a)redhat.com> Cc: Mark Langsdorf <mlangsdo(a)redhat.com> Cc: Jeremy Linton <jlinton(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_ARCH_N5X b/redhat/configs/common/generic/CONFIG_ARCH_N5X --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_ARCH_N5X @@ -0,0 +1 @@ +# CONFIG_ARCH_N5X is not set diff a/redhat/configs/pending-common/generic/CONFIG_ARCH_N5X b/redhat/configs/pending-common/generic/CONFIG_ARCH_N5X --- a/redhat/configs/pending-common/generic/CONFIG_ARCH_N5X +++ /dev/null @@ -1,14 +0,0 @@ -# CONFIG_ARCH_N5X: -# -# This enables support for Intel's eASIC N5X SoCFPGA Family. -# -# Symbol: ARCH_N5X [=n] -# Type : bool -# Defined at arch/arm64/Kconfig.platforms:16 -# Prompt: Intel's eASIC N5X SoCFPGA Family -# Location: -# -> Platform selection -# -# -# -# CONFIG_ARCH_N5X is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/899

2 1

[OS-BUILD PATCH] [redhat] New configs in net/netfilter
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in net/netfilter Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_IP_VS_TWOS: The weighted random twos choice least-connection scheduling algorithm picks two random real servers and directs network connections to the server with the least active connections normalized by the server weight. If you want to compile it in kernel, say Y. To compile it as a module, choose M here. If unsure, say N. Symbol: IP_VS_TWOS [=n] Type : tristate Defined at net/netfilter/ipvs/Kconfig:274 Prompt: weighted random twos choice least-connection scheduling Depends on: NET [=y] && NETFILTER [=y] && IP_VS [=m] Location: -> Networking support (NET [=y]) -> Networking options -> Network packet filtering framework (Netfilter) (NETFILTER [=y]) -> IP virtual server support (IP_VS [=m]) --- Cc: Florian Westphal <fwestpha(a)redhat.com> Cc: Jiri Benc <jbenc(a)redhat.com> Cc: Marcelo Leitner <mleitner(a)redhat.com> Cc: Antoine Tenart <atenart(a)redhat.com> Cc: Balazs Nemeth <bnemeth(a)redhat.com> Cc: Davide Caratti <dcaratti(a)redhat.com> Cc: Eric Garver <egarver(a)redhat.com> Cc: Flavio Leitner <fbl(a)redhat.com> Cc: Guillaume Nault <gnault(a)redhat.com> Cc: Hangbin Liu <haliu(a)redhat.com> Cc: Ivan Vecera <ivecera(a)redhat.com> Cc: Jarod Wilson <jarod(a)redhat.com> Cc: Lorenzo Bianconi <lorenzo.bianconi(a)redhat.com> Cc: Paolo Abeni <pabeni(a)redhat.com> Cc: Phil Sutter <psutter(a)redhat.com> Cc: Sabrina Dubroca <sdubroca(a)redhat.com> Cc: Stefano Brivio <sbrivio(a)redhat.com> Cc: Xin Long <lxin(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_IP_VS_TWOS b/redhat/configs/common/generic/CONFIG_IP_VS_TWOS --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_IP_VS_TWOS @@ -0,0 +1 @@ +# CONFIG_IP_VS_TWOS is not set diff a/redhat/configs/pending-common/generic/CONFIG_IP_VS_TWOS b/redhat/configs/pending-common/generic/CONFIG_IP_VS_TWOS --- a/redhat/configs/pending-common/generic/CONFIG_IP_VS_TWOS +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_IP_VS_TWOS: -# -# The weighted random twos choice least-connection scheduling -# algorithm picks two random real servers and directs network -# connections to the server with the least active connections -# normalized by the server weight. -# -# If you want to compile it in kernel, say Y. To compile it as a -# module, choose M here. If unsure, say N. -# -# Symbol: IP_VS_TWOS [=n] -# Type : tristate -# Defined at net/netfilter/ipvs/Kconfig:274 -# Prompt: weighted random twos choice least-connection scheduling -# Depends on: NET [=y] && NETFILTER [=y] && IP_VS [=m] -# Location: -# -> Networking support (NET [=y]) -# -> Networking options -# -> Network packet filtering framework (Netfilter) (NETFILTER [=y]) -# -> IP virtual server support (IP_VS [=m]) -# -# -# -# CONFIG_IP_VS_TWOS is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/913

2 1

[OS-BUILD PATCH] [redhat] New configs in drivers/net/wireless
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/net/wireless Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_MT7921E: This adds support for MT7921E 802.11ax 2x2:2SS wireless devices. To compile this driver as a module, choose M here. Symbol: MT7921E [=n] Type : tristate Defined at drivers/net/wireless/mediatek/mt76/mt7921/Kconfig:2 Prompt: MediaTek MT7921E (PCIe) support Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_MEDIATEK [=y] && MAC80211 [=m] && PCI [=y] Location: -> Device Drivers -> Network device support (NETDEVICES [=y]) -> Wireless LAN (WLAN [=y]) -> MediaTek devices (WLAN_VENDOR_MEDIATEK [=y]) Selects: MT76_CONNAC_LIB [=n] && WANT_DEV_COREDUMP [=y] --- Cc: Jarod Wilson <jarod(a)redhat.com> Cc: John Linville <linville(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_MT7921E b/redhat/configs/common/generic/CONFIG_MT7921E --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_MT7921E @@ -0,0 +1 @@ +# CONFIG_MT7921E is not set diff a/redhat/configs/pending-common/generic/CONFIG_MT7921E b/redhat/configs/pending-common/generic/CONFIG_MT7921E --- a/redhat/configs/pending-common/generic/CONFIG_MT7921E +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_MT7921E: -# -# This adds support for MT7921E 802.11ax 2x2:2SS wireless devices. -# -# To compile this driver as a module, choose M here. -# -# Symbol: MT7921E [=n] -# Type : tristate -# Defined at drivers/net/wireless/mediatek/mt76/mt7921/Kconfig:2 -# Prompt: MediaTek MT7921E (PCIe) support -# Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_MEDIATEK [=y] && MAC80211 [=m] && PCI [=y] -# Location: -# -> Device Drivers -# -> Network device support (NETDEVICES [=y]) -# -> Wireless LAN (WLAN [=y]) -# -> MediaTek devices (WLAN_VENDOR_MEDIATEK [=y]) -# Selects: MT76_CONNAC_LIB [=n] && WANT_DEV_COREDUMP [=y] -# -# -# -# CONFIG_MT7921E is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/909

2 1

[OS-BUILD PATCH] [redhat] New configs in drivers/char
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/char Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_TCG_TIS_I2C_CR50: This is a driver for the Google cr50 I2C TPM interface which is a custom microcontroller and requires a custom i2c protocol interface to handle the limitations of the hardware. To compile this driver as a module, choose M here; the module will be called tcg_tis_i2c_cr50. Symbol: TCG_TIS_I2C_CR50 [=n] Type : tristate Defined at drivers/char/tpm/Kconfig:89 Prompt: TPM Interface Specification 2.0 Interface (I2C - CR50) Depends on: TCG_TPM [=y] && I2C [=y] Location: -> Device Drivers -> Character devices -> TPM Hardware Support (TCG_TPM [=y]) Selects: TCG_CR50 --- Cc: John Linville <linville(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_TCG_TIS_I2C_CR50 b/redhat/configs/common/generic/CONFIG_TCG_TIS_I2C_CR50 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_TCG_TIS_I2C_CR50 @@ -0,0 +1 @@ +# CONFIG_TCG_TIS_I2C_CR50 is not set diff a/redhat/configs/pending-common/generic/CONFIG_TCG_TIS_I2C_CR50 b/redhat/configs/pending-common/generic/CONFIG_TCG_TIS_I2C_CR50 --- a/redhat/configs/pending-common/generic/CONFIG_TCG_TIS_I2C_CR50 +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_TCG_TIS_I2C_CR50: -# -# This is a driver for the Google cr50 I2C TPM interface which is a -# custom microcontroller and requires a custom i2c protocol interface -# to handle the limitations of the hardware. To compile this driver -# as a module, choose M here; the module will be called tcg_tis_i2c_cr50. -# -# Symbol: TCG_TIS_I2C_CR50 [=n] -# Type : tristate -# Defined at drivers/char/tpm/Kconfig:89 -# Prompt: TPM Interface Specification 2.0 Interface (I2C - CR50) -# Depends on: TCG_TPM [=y] && I2C [=y] -# Location: -# -> Device Drivers -# -> Character devices -# -> TPM Hardware Support (TCG_TPM [=y]) -# Selects: TCG_CR50 -# -# -# -# CONFIG_TCG_TIS_I2C_CR50 is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/902

2 1

[OS-BUILD PATCH] [redhat] New configs in sound/core
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in sound/core Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_SND_JACK_INJECTION_DEBUG: This option can be used to enable or disable sound jack software injection. Say Y if you are debugging via jack injection interface. If unsure select "N". Symbol: SND_JACK_INJECTION_DEBUG [=n] Type : bool Defined at sound/core/Kconfig:190 Prompt: Sound jack injection interface via debugfs Depends on: SOUND [=m] && !UML && SND [=m] && SND_JACK [=y] && SND_DEBUG [=y] && DEBUG_FS [=y] Location: -> Device Drivers -> Sound card support (SOUND [=m]) -> Advanced Linux Sound Architecture (SND [=m]) -> Debug (SND_DEBUG [=y]) --- Cc: Jaroslav Kysela <jkysela(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_SND_JACK_INJECTION_DEBUG b/redhat/configs/common/generic/CONFIG_SND_JACK_INJECTION_DEBUG --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_SND_JACK_INJECTION_DEBUG @@ -0,0 +1 @@ +# CONFIG_SND_JACK_INJECTION_DEBUG is not set diff a/redhat/configs/pending-common/generic/CONFIG_SND_JACK_INJECTION_DEBUG b/redhat/configs/pending-common/generic/CONFIG_SND_JACK_INJECTION_DEBUG --- a/redhat/configs/pending-common/generic/CONFIG_SND_JACK_INJECTION_DEBUG +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_SND_JACK_INJECTION_DEBUG: -# -# This option can be used to enable or disable sound jack -# software injection. -# Say Y if you are debugging via jack injection interface. -# If unsure select "N". -# -# Symbol: SND_JACK_INJECTION_DEBUG [=n] -# Type : bool -# Defined at sound/core/Kconfig:190 -# Prompt: Sound jack injection interface via debugfs -# Depends on: SOUND [=m] && !UML && SND [=m] && SND_JACK [=y] && SND_DEBUG [=y] && DEBUG_FS [=y] -# Location: -# -> Device Drivers -# -> Sound card support (SOUND [=m]) -# -> Advanced Linux Sound Architecture (SND [=m]) -# -> Debug (SND_DEBUG [=y]) -# -# -# -# CONFIG_SND_JACK_INJECTION_DEBUG is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/914

2 1

[OS-BUILD PATCH] [redhat] New configs in kernel/trace
by GitLab Bridge on behalf of redhat-patchlab 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_FTRACE_RECORD_RECURSION: All callbacks that attach to the function tracing have some sort of protection against recursion. Even though the protection exists, it adds overhead. This option will create a file in the tracefs file system called "recursed_functions" that will list the functions that triggered a recursion. This will add more overhead to cases that have recursion. If unsure, say N Symbol: FTRACE_RECORD_RECURSION [=n] Type : bool Defined at kernel/trace/Kconfig:737 Prompt: Record functions that recurse in function tracing Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && FUNCTION_TRACER [=y] Location: -> Kernel hacking -> Tracers (FTRACE [=y]) --- CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS: This will audit the time stamps on the ring buffer sub buffer to make sure that all the time deltas for the events on a sub buffer matches the current time stamp. This audit is performed for every event that is not interrupted, or interrupting another event. A check is also made when traversing sub buffers to make sure that all the deltas on the previous sub buffer do not add up to be greater than the current time stamp. NOTE: This adds significant overhead to recording of events, and should only be used to test the logic of the ring buffer. Do not use it on production systems. Only say Y if you understand what this does, and you still want it enabled. Otherwise say N Symbol: RING_BUFFER_VALIDATE_TIME_DELTAS [=n] Type : bool Defined at kernel/trace/Kconfig:846 Prompt: Verify ring buffer time stamp deltas Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && RING_BUFFER [=y] Location: -> Kernel hacking -> Tracers (FTRACE [=y]) --- Cc: Jerome Marchand <jmarchan(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../generic/CONFIG_FTRACE_RECORD_RECURSION | 1 + .../CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS | 1 + .../generic/CONFIG_FTRACE_RECORD_RECURSION | 24 --------------- .../CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS | 30 ------------------- 4 files changed, 2 insertions(+), 54 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_FTRACE_RECORD_RECURSION create mode 100644 redhat/configs/common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS delete mode 100644 redhat/configs/pending-common/generic/CONFIG_FTRACE_RECORD_RECURSION delete mode 100644 redhat/configs/pending-common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS diff --git a/redhat/configs/common/generic/CONFIG_FTRACE_RECORD_RECURSION b/redhat/configs/common/generic/CONFIG_FTRACE_RECORD_RECURSION new file mode 100644 index 000000000000..613dd9d01aef --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_FTRACE_RECORD_RECURSION @@ -0,0 +1 @@ +# CONFIG_FTRACE_RECORD_RECURSION is not set diff --git a/redhat/configs/common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS b/redhat/configs/common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS new file mode 100644 index 000000000000..062dee43468f --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS @@ -0,0 +1 @@ +# CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_FTRACE_RECORD_RECURSION b/redhat/configs/pending-common/generic/CONFIG_FTRACE_RECORD_RECURSION deleted file mode 100644 index d4b4d5a8a0da..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_FTRACE_RECORD_RECURSION +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_FTRACE_RECORD_RECURSION: -# -# All callbacks that attach to the function tracing have some sort -# of protection against recursion. Even though the protection exists, -# it adds overhead. This option will create a file in the tracefs -# file system called "recursed_functions" that will list the functions -# that triggered a recursion. -# -# This will add more overhead to cases that have recursion. -# -# If unsure, say N -# -# Symbol: FTRACE_RECORD_RECURSION [=n] -# Type : bool -# Defined at kernel/trace/Kconfig:737 -# Prompt: Record functions that recurse in function tracing -# Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && FUNCTION_TRACER [=y] -# Location: -# -> Kernel hacking -# -> Tracers (FTRACE [=y]) -# -# -# -# CONFIG_FTRACE_RECORD_RECURSION is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS b/redhat/configs/pending-common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS deleted file mode 100644 index 383636599d30..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS +++ /dev/null @@ -1,30 +0,0 @@ -# CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS: -# -# This will audit the time stamps on the ring buffer sub -# buffer to make sure that all the time deltas for the -# events on a sub buffer matches the current time stamp. -# This audit is performed for every event that is not -# interrupted, or interrupting another event. A check -# is also made when traversing sub buffers to make sure -# that all the deltas on the previous sub buffer do not -# add up to be greater than the current time stamp. -# -# NOTE: This adds significant overhead to recording of events, -# and should only be used to test the logic of the ring buffer. -# Do not use it on production systems. -# -# Only say Y if you understand what this does, and you -# still want it enabled. Otherwise say N -# -# Symbol: RING_BUFFER_VALIDATE_TIME_DELTAS [=n] -# Type : bool -# Defined at kernel/trace/Kconfig:846 -# Prompt: Verify ring buffer time stamp deltas -# Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && RING_BUFFER [=y] -# Location: -# -> Kernel hacking -# -> Tracers (FTRACE [=y]) -# -# -# -# CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS is not set -- GitLab

2 2

[OS-BUILD PATCH] [redhat] New configs in drivers/acpi
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/acpi Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_ACPI_PLATFORM_PROFILE: This driver adds support for platform-profiles on platforms that support it. Platform-profiles can be used to control the platform behaviour. For example whether to operate in a lower power mode, in a higher power performance mode or between the two. This driver provides the sysfs interface and is used as the registration point for platform specific drivers. Which profiles are supported is determined on a per-platform basis and should be obtained from the platform specific driver. Symbol: ACPI_PLATFORM_PROFILE [=m] Type : tristate Defined at drivers/acpi/Kconfig:329 Prompt: ACPI Platform Profile Driver Depends on: ACPI [=y] Location: -> Power management and ACPI options -> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y]) --- Cc: Al Stone <ahs3(a)redhat.com> Cc: Lenny Szubowicz <lszubowi(a)redhat.com> Cc: Prarit Bhargava <prarit(a)redhat.com> Cc: David Arcari <darcari(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_ACPI_PLATFORM_PROFILE b/redhat/configs/common/generic/CONFIG_ACPI_PLATFORM_PROFILE --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_ACPI_PLATFORM_PROFILE @@ -0,0 +1 @@ +CONFIG_ACPI_PLATFORM_PROFILE=m diff a/redhat/configs/pending-common/generic/CONFIG_ACPI_PLATFORM_PROFILE b/redhat/configs/pending-common/generic/CONFIG_ACPI_PLATFORM_PROFILE --- a/redhat/configs/pending-common/generic/CONFIG_ACPI_PLATFORM_PROFILE +++ /dev/null @@ -1,27 +0,0 @@ -# CONFIG_ACPI_PLATFORM_PROFILE: -# -# This driver adds support for platform-profiles on platforms that -# support it. -# -# Platform-profiles can be used to control the platform behaviour. For -# example whether to operate in a lower power mode, in a higher -# power performance mode or between the two. -# -# This driver provides the sysfs interface and is used as the registration -# point for platform specific drivers. -# -# Which profiles are supported is determined on a per-platform basis and -# should be obtained from the platform specific driver. -# -# Symbol: ACPI_PLATFORM_PROFILE [=m] -# Type : tristate -# Defined at drivers/acpi/Kconfig:329 -# Prompt: ACPI Platform Profile Driver -# Depends on: ACPI [=y] -# Location: -# -> Power management and ACPI options -# -> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y]) -# -# -# -CONFIG_ACPI_PLATFORM_PROFILE=m -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/901

2 1

[OS-BUILD PATCH] Bluetooth: L2CAP: Try harder to accept device not knowing options
by Bastien Nocera (via Email Bridge) 22 Feb '21

22 Feb '21

From: Bastien Nocera <hadess(a)hadess.net> Bluetooth: L2CAP: Try harder to accept device not knowing options The current implementation of L2CAP options negotiation will continue the negotiation when a device responds with L2CAP_CONF_UNACCEPT ("unaccepted options"), but not when the device replies with L2CAP_CONF_UNKNOWN ("unknown options"). Trying to continue the negotiation without ERTM support will allow Bluetooth-capable XBox One controllers (notably models 1708 and 1797) to connect. btmon before patch: > ACL Data RX: Handle 256 flags 0x02 dlen 16 #64 [hci0] 59.182702 L2CAP: Connection Response (0x03) ident 2 len 8 Destination CID: 64 Source CID: 64 Result: Connection successful (0x0000) Status: No further information available (0x0000) < ACL Data TX: Handle 256 flags 0x00 dlen 23 #65 [hci0] 59.182744 L2CAP: Configure Request (0x04) ident 3 len 15 Destination CID: 64 Flags: 0x0000 Option: Retransmission and Flow Control (0x04) [mandatory] Mode: Basic (0x00) TX window size: 0 Max transmit: 0 Retransmission timeout: 0 Monitor timeout: 0 Maximum PDU size: 0 > ACL Data RX: Handle 256 flags 0x02 dlen 16 #66 [hci0] 59.183948 L2CAP: Configure Request (0x04) ident 1 len 8 Destination CID: 64 Flags: 0x0000 Option: Maximum Transmission Unit (0x01) [mandatory] MTU: 1480 < ACL Data TX: Handle 256 flags 0x00 dlen 18 #67 [hci0] 59.183994 L2CAP: Configure Response (0x05) ident 1 len 10 Source CID: 64 Flags: 0x0000 Result: Success (0x0000) Option: Maximum Transmission Unit (0x01) [mandatory] MTU: 1480 > ACL Data RX: Handle 256 flags 0x02 dlen 15 #69 [hci0] 59.187676 L2CAP: Configure Response (0x05) ident 3 len 7 Source CID: 64 Flags: 0x0000 Result: Failure - unknown options (0x0003) 04 . < ACL Data TX: Handle 256 flags 0x00 dlen 12 #70 [hci0] 59.187722 L2CAP: Disconnection Request (0x06) ident 4 len 4 Destination CID: 64 Source CID: 64 > ACL Data RX: Handle 256 flags 0x02 dlen 12 #73 [hci0] 59.192714 L2CAP: Disconnection Response (0x07) ident 4 len 4 Destination CID: 64 Source CID: 64 btmon after patch: > ACL Data RX: Handle 256 flags 0x02 dlen 16 #248 [hci0] 103.502970 L2CAP: Connection Response (0x03) ident 5 len 8 Destination CID: 65 Source CID: 65 Result: Connection pending (0x0001) Status: No further information available (0x0000) > ACL Data RX: Handle 256 flags 0x02 dlen 16 #249 [hci0] 103.504184 L2CAP: Connection Response (0x03) ident 5 len 8 Destination CID: 65 Source CID: 65 Result: Connection successful (0x0000) Status: No further information available (0x0000) < ACL Data TX: Handle 256 flags 0x00 dlen 23 #250 [hci0] 103.504398 L2CAP: Configure Request (0x04) ident 6 len 15 Destination CID: 65 Flags: 0x0000 Option: Retransmission and Flow Control (0x04) [mandatory] Mode: Basic (0x00) TX window size: 0 Max transmit: 0 Retransmission timeout: 0 Monitor timeout: 0 Maximum PDU size: 0 > ACL Data RX: Handle 256 flags 0x02 dlen 16 #251 [hci0] 103.505472 L2CAP: Configure Request (0x04) ident 3 len 8 Destination CID: 65 Flags: 0x0000 Option: Maximum Transmission Unit (0x01) [mandatory] MTU: 1480 < ACL Data TX: Handle 256 flags 0x00 dlen 18 #252 [hci0] 103.505689 L2CAP: Configure Response (0x05) ident 3 len 10 Source CID: 65 Flags: 0x0000 Result: Success (0x0000) Option: Maximum Transmission Unit (0x01) [mandatory] MTU: 1480 > ACL Data RX: Handle 256 flags 0x02 dlen 15 #254 [hci0] 103.509165 L2CAP: Configure Response (0x05) ident 6 len 7 Source CID: 65 Flags: 0x0000 Result: Failure - unknown options (0x0003) 04 . < ACL Data TX: Handle 256 flags 0x00 dlen 12 #255 [hci0] 103.509426 L2CAP: Configure Request (0x04) ident 7 len 4 Destination CID: 65 Flags: 0x0000 < ACL Data TX: Handle 256 flags 0x00 dlen 12 #257 [hci0] 103.511870 L2CAP: Connection Request (0x02) ident 8 len 4 PSM: 1 (0x0001) Source CID: 66 > ACL Data RX: Handle 256 flags 0x02 dlen 14 #259 [hci0] 103.514121 L2CAP: Configure Response (0x05) ident 7 len 6 Source CID: 65 Flags: 0x0000 Result: Success (0x0000) Upstream Status: bluetooth/bluetooth-next.git (cherry picked from commit 98d2c3e1731007acf03addf83c863df6694beb95) Signed-off-by: Bastien Nocera <hadess(a)hadess.net> Signed-off-by: Florian Dollinger <dollinger.florian(a)gmx.de> Co-developed-by: Florian Dollinger <dollinger.florian(a)gmx.de> Reviewed-by: Luiz Augusto Von Dentz <luiz.von.dentz(a)intel.com> Signed-off-by: Marcel Holtmann <marcel(a)holtmann.org> diff a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c --- a/net/bluetooth/l2cap_core.c +++ b/net/bluetooth/l2cap_core.c @@ -4519,6 +4519,7 @@ static inline int l2cap_config_rsp(struct l2cap_conn *conn, } goto done; + case L2CAP_CONF_UNKNOWN: case L2CAP_CONF_UNACCEPT: if (chan->num_conf_rsp <= L2CAP_CONF_MAX_CONF_RSP) { char req[64]; -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/872

3 6

[OS-BUILD PATCH] [redhat] New configs in drivers/powercap
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/powercap Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_DTPM: This enables support for the power capping for the dynamic thermal power management userspace engine. Symbol: DTPM [=n] Type : bool Defined at drivers/powercap/Kconfig:47 Prompt: Power capping for Dynamic Thermal Power Management Depends on: POWERCAP [=y] Location: -> Device Drivers -> Generic powercap sysfs driver (POWERCAP [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_DTPM b/redhat/configs/common/generic/CONFIG_DTPM --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_DTPM @@ -0,0 +1 @@ +# CONFIG_DTPM is not set diff a/redhat/configs/pending-common/generic/CONFIG_DTPM b/redhat/configs/pending-common/generic/CONFIG_DTPM --- a/redhat/configs/pending-common/generic/CONFIG_DTPM +++ /dev/null @@ -1,17 +0,0 @@ -# CONFIG_DTPM: -# -# This enables support for the power capping for the dynamic -# thermal power management userspace engine. -# -# Symbol: DTPM [=n] -# Type : bool -# Defined at drivers/powercap/Kconfig:47 -# Prompt: Power capping for Dynamic Thermal Power Management -# Depends on: POWERCAP [=y] -# Location: -# -> Device Drivers -# -> Generic powercap sysfs driver (POWERCAP [=y]) -# -# -# -# CONFIG_DTPM is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/910

1 0

[OS-BUILD PATCH] [redhat] New configs in drivers/net/ethernet/mellanox
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/net/ethernet/mellanox Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_MLX5_SF: Build support for subfuction device in the NIC. A Mellanox subfunction device can support RDMA, netdevice and vdpa device. It is similar to a SRIOV VF but it doesn't require SRIOV support. Symbol: MLX5_SF [=n] Type : bool Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:205 Prompt: Mellanox Technologies subfunction device support using auxiliary device Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_CORE [=m] && MLX5_CORE_EN [=y] Location: -> Device Drivers -> Network device support (NETDEVICES [=y]) -> Ethernet driver support (ETHERNET [=y]) -> Mellanox devices (NET_VENDOR_MELLANOX [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_MLX5_SF b/redhat/configs/common/generic/CONFIG_MLX5_SF --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_MLX5_SF @@ -0,0 +1 @@ +# CONFIG_MLX5_SF is not set diff a/redhat/configs/pending-common/generic/CONFIG_MLX5_SF b/redhat/configs/pending-common/generic/CONFIG_MLX5_SF --- a/redhat/configs/pending-common/generic/CONFIG_MLX5_SF +++ /dev/null @@ -1,20 +0,0 @@ -# CONFIG_MLX5_SF: -# -# Build support for subfuction device in the NIC. A Mellanox subfunction -# device can support RDMA, netdevice and vdpa device. -# It is similar to a SRIOV VF but it doesn't require SRIOV support. -# -# Symbol: MLX5_SF [=n] -# Type : bool -# Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:205 -# Prompt: Mellanox Technologies subfunction device support using auxiliary device -# Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_CORE [=m] && MLX5_CORE_EN [=y] -# Location: -# -> Device Drivers -# -> Network device support (NETDEVICES [=y]) -# -> Ethernet driver support (ETHERNET [=y]) -# -> Mellanox devices (NET_VENDOR_MELLANOX [=y]) -# -# -# -# CONFIG_MLX5_SF is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/908

1 0

[OS-BUILD PATCH] [redhat] New configs in drivers/leds
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/leds Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_LEDS_TRIGGER_TTY: This allows LEDs to be controlled by activity on ttys which includes serial devices like /dev/ttyS0. When build as a module this driver will be called ledtrig-tty. Symbol: LEDS_TRIGGER_TTY [=n] Type : tristate Defined at drivers/leds/trigger/Kconfig:147 Prompt: LED Trigger for TTY devices Depends on: NEW_LEDS [=y] && LEDS_TRIGGERS [=y] && TTY [=y] Location: -> Device Drivers -> LED Support (NEW_LEDS [=y]) -> LED Trigger support (LEDS_TRIGGERS [=y]) --- Cc: Tony Camuso <tcamuso(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_LEDS_TRIGGER_TTY b/redhat/configs/common/generic/CONFIG_LEDS_TRIGGER_TTY --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_LEDS_TRIGGER_TTY @@ -0,0 +1 @@ +# CONFIG_LEDS_TRIGGER_TTY is not set diff a/redhat/configs/pending-common/generic/CONFIG_LEDS_TRIGGER_TTY b/redhat/configs/pending-common/generic/CONFIG_LEDS_TRIGGER_TTY --- a/redhat/configs/pending-common/generic/CONFIG_LEDS_TRIGGER_TTY +++ /dev/null @@ -1,20 +0,0 @@ -# CONFIG_LEDS_TRIGGER_TTY: -# -# This allows LEDs to be controlled by activity on ttys which includes -# serial devices like /dev/ttyS0. -# -# When build as a module this driver will be called ledtrig-tty. -# -# Symbol: LEDS_TRIGGER_TTY [=n] -# Type : tristate -# Defined at drivers/leds/trigger/Kconfig:147 -# Prompt: LED Trigger for TTY devices -# Depends on: NEW_LEDS [=y] && LEDS_TRIGGERS [=y] && TTY [=y] -# Location: -# -> Device Drivers -# -> LED Support (NEW_LEDS [=y]) -# -> LED Trigger support (LEDS_TRIGGERS [=y]) -# -# -# -# CONFIG_LEDS_TRIGGER_TTY is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/905

1 0

[OS-BUILD PATCH] [redhat] New configs in drivers/iio
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/iio Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_AD5766: Say yes here to build support for Analog Devices AD5766, AD5767 Digital to Analog Converter. To compile this driver as a module, choose M here: the module will be called ad5766. Symbol: AD5766 [=n] Type : tristate Defined at drivers/iio/dac/Kconfig:192 Prompt: Analog Devices AD5766/AD5767 DAC driver Depends on: IIO [=m] && SPI_MASTER [=y] Location: -> Device Drivers -> Industrial I/O support (IIO [=m]) -> Digital to analog converters --- CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE: This sensor present three angles, hinge angel, screen angles and keyboard angle respect to horizon (ground). Say yes here to build support for the HID custom intel hinge sensor. To compile this driver as a module, choose M here: the module will be called hid-sensor-custom-hinge. Symbol: HID_SENSOR_CUSTOM_INTEL_HINGE [=n] Type : tristate Defined at drivers/iio/position/Kconfig:19 Prompt: HID Hinge Depends on: IIO [=m] && HID_SENSOR_HUB [=y] Location: -> Device Drivers -> Industrial I/O support (IIO [=m]) -> Linear and angular position sensors Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] && HID_SENSOR_IIO_COMMON [=m] && HID_SENSOR_IIO_TRIGGER [=m] --- CONFIG_YAMAHA_YAS530: Say Y here to add support for the Yamaha YAS530 series of 3-Axis Magnetometers. Right now YAS530, YAS532 and YAS533 are fully supported. This driver can also be compiled as a module. To compile this driver as a module, choose M here: the module will be called yamaha-yas. Symbol: YAMAHA_YAS530 [=n] Type : tristate Defined at drivers/iio/magnetometer/Kconfig:208 Prompt: Yamaha YAS530 family of 3-Axis Magnetometers (I2C) Depends on: IIO [=m] && I2C [=y] Location: -> Device Drivers -> Industrial I/O support (IIO [=m]) -> Magnetometer sensors Selects: REGMAP_I2C [=m] && IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_AD5766 b/redhat/configs/common/generic/CONFIG_AD5766 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_AD5766 @@ -0,0 +1 @@ +# CONFIG_AD5766 is not set diff a/redhat/configs/common/generic/CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE b/redhat/configs/common/generic/CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE @@ -0,0 +1 @@ +# CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE is not set diff a/redhat/configs/common/generic/CONFIG_YAMAHA_YAS530 b/redhat/configs/common/generic/CONFIG_YAMAHA_YAS530 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_YAMAHA_YAS530 @@ -0,0 +1 @@ +# CONFIG_YAMAHA_YAS530 is not set diff a/redhat/configs/pending-common/generic/CONFIG_AD5766 b/redhat/configs/pending-common/generic/CONFIG_AD5766 --- a/redhat/configs/pending-common/generic/CONFIG_AD5766 +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_AD5766: -# -# Say yes here to build support for Analog Devices AD5766, AD5767 -# Digital to Analog Converter. -# -# To compile this driver as a module, choose M here: the -# module will be called ad5766. -# -# Symbol: AD5766 [=n] -# Type : tristate -# Defined at drivers/iio/dac/Kconfig:192 -# Prompt: Analog Devices AD5766/AD5767 DAC driver -# Depends on: IIO [=m] && SPI_MASTER [=y] -# Location: -# -> Device Drivers -# -> Industrial I/O support (IIO [=m]) -# -> Digital to analog converters -# -# -# -# CONFIG_AD5766 is not set diff a/redhat/configs/pending-common/generic/CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE b/redhat/configs/pending-common/generic/CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE --- a/redhat/configs/pending-common/generic/CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE: -# -# This sensor present three angles, hinge angel, screen angles -# and keyboard angle respect to horizon (ground). -# Say yes here to build support for the HID custom -# intel hinge sensor. -# -# To compile this driver as a module, choose M here: the -# module will be called hid-sensor-custom-hinge. -# -# Symbol: HID_SENSOR_CUSTOM_INTEL_HINGE [=n] -# Type : tristate -# Defined at drivers/iio/position/Kconfig:19 -# Prompt: HID Hinge -# Depends on: IIO [=m] && HID_SENSOR_HUB [=y] -# Location: -# -> Device Drivers -# -> Industrial I/O support (IIO [=m]) -# -> Linear and angular position sensors -# Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] && HID_SENSOR_IIO_COMMON [=m] && HID_SENSOR_IIO_TRIGGER [=m] -# -# -# -# CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE is not set diff a/redhat/configs/pending-common/generic/CONFIG_YAMAHA_YAS530 b/redhat/configs/pending-common/generic/CONFIG_YAMAHA_YAS530 --- a/redhat/configs/pending-common/generic/CONFIG_YAMAHA_YAS530 +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_YAMAHA_YAS530: -# -# Say Y here to add support for the Yamaha YAS530 series of -# 3-Axis Magnetometers. Right now YAS530, YAS532 and YAS533 are -# fully supported. -# -# This driver can also be compiled as a module. -# To compile this driver as a module, choose M here: the module -# will be called yamaha-yas. -# -# Symbol: YAMAHA_YAS530 [=n] -# Type : tristate -# Defined at drivers/iio/magnetometer/Kconfig:208 -# Prompt: Yamaha YAS530 family of 3-Axis Magnetometers (I2C) -# Depends on: IIO [=m] && I2C [=y] -# Location: -# -> Device Drivers -# -> Industrial I/O support (IIO [=m]) -# -> Magnetometer sensors -# Selects: REGMAP_I2C [=m] && IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m] -# -# -# -# CONFIG_YAMAHA_YAS530 is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/904

1 0

Rawhide kernels have CONFIG_USB_RTL8152 unset causing ethernet to not work on many docking-stations ?
by Hans de Goede 19 Feb '21

19 Feb '21

Hi All, I'm sending out an email about this as I'm not 100% sure how to fix this. As a kernel-developer I usually build my own local kernels, since I'm also a Fedora developer I try to keep the kernel .config of my local builds synced with the Fedora kernel-configs. When grabbing the config from the kernel-core-5.11.0-0.rc6.141.fc34.x86_64.rpm pkg and comparing it to my local config I noticed this: # CONFIG_USB_RTL8152 is not set And I immediately thought that can't be right, that is used in my Lenovo Thunderbolt docking station gen 2. It took me some digging to figure out what is going on here: [hans@x1 kernel-ark]$ pwd /home/hans/projects/kernel-ark [hans@x1 kernel-ark]$ find -name CONFIG_USB_RTL8152 ./redhat/configs/common/generic/CONFIG_USB_RTL8152 [hans@x1 kernel-ark]$ cat ./redhat/configs/common/generic/CONFIG_USB_RTL8152 CONFIG_USB_RTL8152=m That looks good, but is not what is in the rawhide-build, digging deeper finds this: [hans@x1 rawhide]$ pwd /home/hans/projects/fedora/kernel/rawhide [hans@x1 rawhide]$ grep CONFIG_USB_RTL8152 kernel-x86_64-fedora.config # CONFIG_USB_RTL8152 is not set, or the RTL8153 device is not Which looks weird and then I found this, which explains everything: [hans@x1 kernel-ark]$ cat redhat/configs/fedora/generic/CONFIG_USB_RTL8153_ECM # CONFIG_USB_RTL8153_ECM: # # This option supports ECM mode for RTL8153 ethernet adapter, when # CONFIG_USB_RTL8152 is not set, or the RTL8153 device is not # supported by r8152 driver. # # Symbol: USB_RTL8153_ECM [=m] # Type : tristate # Defined at drivers/net/usb/Kconfig:631 # Prompt: RTL8153 ECM support # Depends on: NETDEVICES [=y] && USB_NET_DRIVERS [=y] && USB_NET_CDCETHER [=m] && (USB_RTL8152 [=m] || USB_RTL8152 [=m]=n) # Location: # -> Device Drivers # -> Network device support (NETDEVICES [=y]) # -> USB Network Adapters (USB_NET_DRIVERS [=y]) # # # CONFIG_USB_RTL8153_ECM=m The script which is creating kernel-x86_64-fedora.config from all the CONFIG_FOO files is picking up the line from the comment block because the line matches the standard "# CONFIG_FOO is not set" template (with extra text at the end). Interestingly enough, I also see this: [hans@x1 kernel-ark]$ grep CONFIG_USB_RTL8152 redhat/configs/kernel-x86_64-fedora.config CONFIG_USB_RTL8152=m So on the kernel-x86_64-fedora.config in kernel-ark things are ok, but in the kernel-x86_64-fedora.config file in distgit, rawhide branch it is not ok ? I guess there is some difference in how these are generated ? Regards, Hans

2 6

[OS-BUILD PATCH] rpmspec: ship gpio-watch.debug in the proper debuginfo package
by Herton Krzesinski (via Email Bridge) 19 Feb '21

19 Feb '21

From: Herton R. Krzesinski <herton(a)redhat.com> rpmspec: ship gpio-watch.debug in the proper debuginfo package The gpio-watch tool is shipped within the kernel-tools package. However, when it was added some time ago, the debuginfo pattern inside the spec file was not updated, so the gpio-watch.debug file ends up in the kernel-debuginfo-common package instead of the kernel-tools-debuginfo. This change fixes the problem, and also it's likely will fix an update/downgrade test done on CI for RHEL that reports: Error: Transaction test error: file /usr/lib/debug/usr/bin/gpio-watch.debug from install of kernel-debuginfo-common-x86_64-5.11.0-0.rc7.151.el9.x86_64 conflicts with file from package kernel-debuginfo-common-x86_64-5.11.0-1.el9.x86_64 Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com> diff a/redhat/kernel.spec.template b/redhat/kernel.spec.template --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -930,7 +930,7 @@ This package provides debug information for package kernel-tools. # symlinks because of the trailing nonmatching alternation and # the leading .*, because of find-debuginfo.sh's buggy handling # of matching the pattern against the symlinks file. -%{expand:%%global _find_debuginfo_opts %{?_find_debuginfo_opts} -p '.*%%{_bindir}/centrino-decode(\.debug)?|.*%%{_bindir}/powernow-k8-decode(\.debug)?|.*%%{_bindir}/cpupower(\.debug)?|.*%%{_libdir}/libcpupower.*|.*%%{_bindir}/turbostat(\.debug)?|.*%%{_bindir}/x86_energy_perf_policy(\.debug)?|.*%%{_bindir}/tmon(\.debug)?|.*%%{_bindir}/lsgpio(\.debug)?|.*%%{_bindir}/gpio-hammer(\.debug)?|.*%%{_bindir}/gpio-event-mon(\.debug)?|.*%%{_bindir}/iio_event_monitor(\.debug)?|.*%%{_bindir}/iio_generic_buffer(\.debug)?|.*%%{_bindir}/lsiio(\.debug)?|.*%%{_bindir}/intel-speed-select(\.debug)?|XXX' -o kernel-tools-debuginfo.list} +%{expand:%%global _find_debuginfo_opts %{?_find_debuginfo_opts} -p '.*%%{_bindir}/centrino-decode(\.debug)?|.*%%{_bindir}/powernow-k8-decode(\.debug)?|.*%%{_bindir}/cpupower(\.debug)?|.*%%{_libdir}/libcpupower.*|.*%%{_bindir}/turbostat(\.debug)?|.*%%{_bindir}/x86_energy_perf_policy(\.debug)?|.*%%{_bindir}/tmon(\.debug)?|.*%%{_bindir}/lsgpio(\.debug)?|.*%%{_bindir}/gpio-hammer(\.debug)?|.*%%{_bindir}/gpio-event-mon(\.debug)?|.*%%{_bindir}/gpio-watch(\.debug)?|.*%%{_bindir}/iio_event_monitor(\.debug)?|.*%%{_bindir}/iio_generic_buffer(\.debug)?|.*%%{_bindir}/lsiio(\.debug)?|.*%%{_bindir}/intel-speed-select(\.debug)?|XXX' -o kernel-tools-debuginfo.list} # with_tools %endif -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/896

1 0

[OS-BUILD PATCHv3 0/2] [redhat] New configs in net/netfilter
by CKI Gitlab (via Email Bridge) 19 Feb '21

19 Feb '21

From: CKI Gitlab on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/812 Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_NFT_REJECT_NETDEV: This option enables the REJECT support from the netdev table. The return packet generation will be delegated to the IPv4 or IPv6 ICMP or TCP RST implementation depending on the protocol of the packet. Symbol: NFT_REJECT_NETDEV [=n] Type : tristate Defined at net/netfilter/Kconfig:685 Prompt: Netfilter nf_tables netdev REJECT support Depends on: NET [=y] && INET [=y] && NETFILTER [=y] && NF_TABLES [=m] && NF_TABLES_NETDEV [=y] && NFT_REJECT_IPV4 [=m] && NFT_REJECT_IPV6 [=m] Location: -> Networking support (NET [=y]) -> Networking options -> Network packet filtering framework (Netfilter) (NETFILTER [=y]) -> Core Netfilter Configuration -> Netfilter nf_tables support (NF_TABLES [=m]) --- Cc: Florian Westphal <fwestpha(a)redhat.com> Cc: Jiri Benc <jbenc(a)redhat.com> Cc: Marcelo Leitner <mleitner(a)redhat.com> Cc: Davide Caratti <dcaratti(a)redhat.com> Cc: Eric Garver <egarver(a)redhat.com> Cc: Flavio Leitner <fbl(a)redhat.com> Cc: Guillaume Nault <gnault(a)redhat.com> Cc: Hangbin Liu <haliu(a)redhat.com> Cc: Ivan Vecera <ivecera(a)redhat.com> Cc: Jarod Wilson <jarod(a)redhat.com> Cc: Lorenzo Bianconi <lorenzo.bianconi(a)redhat.com> Cc: Paolo Abeni <pabeni(a)redhat.com> Cc: Phil Sutter <psutter(a)redhat.com> Cc: Sabrina Dubroca <sdubroca(a)redhat.com> Cc: Stefano Brivio <sbrivio(a)redhat.com> Cc: Xin Long <lxin(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>

4 5

[OS-BUILD PATCH] [redhat] New configs in drivers/net/ethernet/chelsio
by GitLab Bridge on behalf of jeremycline 18 Feb '21

18 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_CHELSIO_INLINE_CRYPTO: Enable support for inline crypto. Allows enable/disable from list of inline crypto drivers. Symbol: CHELSIO_INLINE_CRYPTO [=y] Type : bool Defined at drivers/net/ethernet/chelsio/inline_crypto/Kconfig:6 Prompt: Chelsio Inline Crypto support Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_CHELSIO [=y] && CHELSIO_T4 [=m] Location: -> Device Drivers -> Network device support (NETDEVICES [=y]) -> Ethernet driver support (ETHERNET [=y]) -> Chelsio devices (NET_VENDOR_CHELSIO [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../generic/CONFIG_CHELSIO_INLINE_CRYPTO | 1 + .../generic/CONFIG_CHELSIO_INLINE_CRYPTO | 19 ------------------- 2 files changed, 1 insertion(+), 19 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_CHELSIO_INLINE_CRYPTO delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CHELSIO_INLINE_CRYPTO diff --git a/redhat/configs/common/generic/CONFIG_CHELSIO_INLINE_CRYPTO b/redhat/configs/common/generic/CONFIG_CHELSIO_INLINE_CRYPTO new file mode 100644 index 000000000000..bd32df3059f2 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_CHELSIO_INLINE_CRYPTO @@ -0,0 +1 @@ +CONFIG_CHELSIO_INLINE_CRYPTO=y diff --git a/redhat/configs/pending-common/generic/CONFIG_CHELSIO_INLINE_CRYPTO b/redhat/configs/pending-common/generic/CONFIG_CHELSIO_INLINE_CRYPTO deleted file mode 100644 index 95b39e771a2a..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_CHELSIO_INLINE_CRYPTO +++ /dev/null @@ -1,19 +0,0 @@ -# CONFIG_CHELSIO_INLINE_CRYPTO: -# -# Enable support for inline crypto. -# Allows enable/disable from list of inline crypto drivers. -# -# Symbol: CHELSIO_INLINE_CRYPTO [=y] -# Type : bool -# Defined at drivers/net/ethernet/chelsio/inline_crypto/Kconfig:6 -# Prompt: Chelsio Inline Crypto support -# Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_CHELSIO [=y] && CHELSIO_T4 [=m] -# Location: -# -> Device Drivers -# -> Network device support (NETDEVICES [=y]) -# -> Ethernet driver support (ETHERNET [=y]) -# -> Chelsio devices (NET_VENDOR_CHELSIO [=y]) -# -# -# -CONFIG_CHELSIO_INLINE_CRYPTO=y -- GitLab

2 1

Bluetooth patch for Fedora 5.11 kernels
by Hans de Goede 18 Feb '21

18 Feb '21

Hi All, The 5.10.y and 5.11.y kernel series have a btusb regression causing various QCA bluetooth adapters to no longer work, see: https://bugzilla.redhat.com/show_bug.cgi?id=1916104 https://bugzilla.kernel.org/show_bug.cgi?id=210681 Unfortunately it is taking quite a long time to get the fix for this into Linus' tree and the stable rules say that only fixes which are in Linus' tree can be cherry-picked into the stable series. To get this fixed for Fedora users now I've added the upstream fix: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.gi… as a downstream patch to the F32/F33 5.10.y kernels. But given the switch to the ark process for the 5.11 kernel I've not touched that. I've attached the patch (as cherry-picked to apply to 5.10.y) here, if someone can add this to the 5.11.y kernels, then that would be great. Regards, Hans

2 1

[OS-BUILD PATCH] [redhat] spec: Add %bcond_with clang option
by Tom Stellard (via Email Bridge) 18 Feb '21

18 Feb '21

From: Tom Stellard <tstellar(a)redhat.com> [redhat] spec: Add %bcond_with clang option diff a/redhat/kernel.spec.template b/redhat/kernel.spec.template --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -6,6 +6,12 @@ # Disable LTO in userspace packages. %global _lto_cflags %{nil} +# Option to enable compiling with clang instead of gcc. +%bcond_with toolchain_clang + +%if %{with toolchain_clang} +%global toolchain clang +%endif # Cross compile on copr for arm # See https://bugzilla.redhat.com/1879599 @@ -228,6 +234,10 @@ Summary: The Linux kernel %define make_opts -s %endif +%if %{with toolchain_clang} +%global make_opts %{make_opts} HOSTCC=clang CC=clang +%endif + # turn off debug kernel and kabichk for gcov builds %if %{with_gcov} %define with_debug 0 @@ -432,6 +442,14 @@ Summary: The Linux kernel %define with_configchecks 0 %endif +# Setting the compiler to clang enables some different config options +# than what is expected, so disable this check for now. +# TODO: What's the best way to fix this? Do wee need a different set of +# configs for clang? +%if %{with toolchain_clang} +%define with_configchecks 0 +%endif + # To temporarily exclude an architecture from being built, add it to # %%nobuildarches. Do _NOT_ use the ExclusiveArch: line, because if we # don't build kernel-headers then the new build system will no longer let @@ -596,6 +614,10 @@ BuildRequires: xmlto BuildRequires: asciidoc %endif +%if %{with toolchain_clang} +BuildRequires: clang +%endif + # Because this is the kernel, it's hard to get a single upstream URL # to represent the base without needing to do a bunch of patching. This # tarball is generated from a src-git tree. If you want to see the -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/894

2 3

✅ PASS: Test report for kernel 5.10.17-200.fc33 (fedora-33)
by CKI Project 18 Feb '21

18 Feb '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.10.17-200.fc33 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=62181060 The results of these automated tests are provided below. Overall result: PASSED Tests: OK All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng Host 2: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity ppc64le: Host 1: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test Host 2: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity s390x: Host 1: ✅ Boot test 🚧 ✅ Storage blktests 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng Host 2: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity x86_64: Host 1: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ xfstests - nfsv4.2 🚧 ✅ xfstests - cifsv3.11 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

Fedora and 5.11 kernels
by Justin Forbes 17 Feb '21

17 Feb '21

With the 5.11 kernel series, I will be moving Fedora stable releases to use the ark process. The branch fedora-5.11 has been pushed. The fedora-5.11 tree is a rebase of os-build onto the linux-5.11.y stable tree. RHEL specific patches around KABI and support are dropped to remain closer to upstream, similar to what Fedora has been using in stable releases for a while now. The initial tree was a rebase, but stable linux-5.11.y updates will be merged. While this is a proper working tree, none of the scripts to create a release are working quite as they should be. I will be getting those fixed up this week, but living in Texas, I only get power in very small bursts which could drop at any time this week. I wanted to get the tree out though, so people can do merge requests for patches or config changes that may be needed. Given the Pacific northwest is also going through power issues, Linus hasn't even started merging for 5.12 yet, so perhaps will will have some time before 5.11.1 comes out. With this process, all changes should be made into the fedora-5.11 tree at https://gitlab.com/cki-project/kernel-ark/-/tree/fedora-5.11, and that will be used to build dist-git. As Fedora 34 is tracking 5.11 until release, I will not be pushing updates to stabilization, but will use F34 to build test kernels against F33 for test week. Thanks, Justin

1 0

Re: Kernel version plans for Fedora 34 ?
by Bastien Nocera 17 Feb '21

17 Feb '21

On Fri, 2021-02-12 at 14:07 +0100, Bastien Nocera wrote: > On Thu, 2021-02-11 at 17:23 -0600, Justin Forbes wrote: > > On Thu, Feb 11, 2021 at 1:01 PM Bastien Nocera <hadess(a)hadess.net> > > wrote: > > > > > > On Thu, 2021-02-11 at 19:32 +0100, Hans de Goede wrote: > > > <snip> > > > > So where do I submit these once backported ? Do I just add > > > > them > > > > to > > > > dist-git > > > > as before ? AFAIK 5.11 will be the first kernel-ark based > > > > Fedora > > > > kernel > > > > (at least 5.10 dist-git does not look ark based), right ? > > > > > > I recently wanted to do that for a Bluetooth patch, and this is > > > how > > > I > > > went about it, along with discussions that happened on the list: > > > https://gitlab.com/cki-project/kernel-ark/-/merge_requests/872 > > > > > > I don't know whether I would have needed to proceed to get this > > > particular patch into stable releases, like Fedora 33 though. > > > > > > > The Fedora stable branches are a bit different, in that they do not > > copy over to ELN, so it is a much less formal process. Basically > > either I take it or I don't. And that is typically determined by a) > > What is the upstream status? b) How invasive is the backport? c) > > What > > is it trying to solve? > > Coming back to the merge request I filed, I think that all 3 of those > questions are answered. > > Do I need to do anything else? A separate merge request? Justin, can you please explain what's needed to land upstream patches into stable versions of Fedora, with the above patch as an example? The merge request I filed against what will be the rawhide kernel has all the 3 bits of information you requested. Is something missing? How do we need to contribute the upstream changes to make it as easy as possible for you, so those patches get into stable kernels quickly? Cheers

2 1

[OS-BUILD PATCH 0/2] 5.11 fedora fixes for ARMv7 and some cleanups around debug for highmem
by pbrobinson (via Email Bridge) 17 Feb '21

17 Feb '21

From: pbrobinson on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/895

2 4

[INFO] Email bridge spam reduction
by Don Zickus 15 Feb '21

15 Feb '21

Hi, A couple of us have been fixing bug in the email bridge in the last week. Most changes won't be noticed. However, one notable exception is 'bot spam' filtering. The email bridge will no longer send emails from the various bots about webhook or other admin things. As a submitter of the MR you will continue to get notifications. I doubt anyone will care other than, less email on this list \o/. Cheers, Don

1 0

[OS-BUILD PATCH 0/5] RHMAINTAINERS: updates for Feb 11 2021
by Prarit Bhargava (via Email Bridge) 15 Feb '21

15 Feb '21

From: Prarit Bhargava on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/893 Add kheib entries for various sections. Signed-off-by: Prarit Bhargava <prarit(a)redhat.com> Changes: 21801ca03a97 (Kamal Heib) RHMAINTAINERS: Add entry for the rdma_rxe driver d2ff594249bf (Kamal Heib) RHMAINTAINERS: Add entry for the siw driver 98326c1af45b (Kamal Heib) RHMAINTAINERS: Add entry for the vmw_pvrdma driver 1fce133ec54b (Kamal Heib) RHMAINTAINERS: Add entry for the efa driver 326ac612ba3b (Kamal Heib) RHMAINTAINERS: Add entry for the bnxt_re driver redhat/rhdocs/MAINTAINERS/RHMAINTAINERS | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+)

2 6

✅ PASS: Test report for kernel 5.10.16-200.fc33 (fedora-33)
by CKI Project 15 Feb '21

15 Feb '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.10.16-200.fc33 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=61896538 The results of these automated tests are provided below. Overall result: PASSED Tests: OK All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ⏱ Boot test ⏱ xfstests - ext4 ⏱ xfstests - xfs ⏱ xfstests - btrfs ⏱ Storage blktests ⏱ Storage block - filesystem fio test ⏱ Storage block - queue scheduler test ⏱ Storage nvme - tcp ⏱ Storage: swraid mdadm raid_module test ⏱ stress: stress-ng Host 2: ⏱ Boot test ⏱ ACPI table test ⏱ LTP ⏱ Loopdev Sanity ⏱ Memory: fork_mem ⏱ Memory function: memfd_create ⏱ AMTU (Abstract Machine Test Utility) ⏱ CIFS Connectathon ⏱ Ethernet drivers sanity ppc64le: Host 1: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test s390x: Host 1: ⏱ Boot test ⏱ Storage blktests ⏱ Storage nvme - tcp ⏱ Storage: swraid mdadm raid_module test ⏱ stress: stress-ng Host 2: ⏱ Boot test ⏱ LTP ⏱ Loopdev Sanity ⏱ Memory: fork_mem ⏱ Memory function: memfd_create ⏱ AMTU (Abstract Machine Test Utility) ⏱ CIFS Connectathon ⏱ Ethernet drivers sanity x86_64: Host 1: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ xfstests - nfsv4.2 🚧 ✅ xfstests - cifsv3.11 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng Host 2: ⏱ Boot test ⏱ ACPI table test ⏱ LTP ⏱ Loopdev Sanity ⏱ Memory: fork_mem ⏱ Memory function: memfd_create ⏱ AMTU (Abstract Machine Test Utility) ⏱ CIFS Connectathon ⏱ Ethernet drivers sanity Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

Kernel version plans for Fedora 34 ?
by Hans de Goede 12 Feb '21

12 Feb '21

Hi, I was wondering with which kernel version we are planning to ship Fedora 34 gold ? I expect 5.12 final to be released on April 19th, which puts it just past the F34 final freeze. So I was wondering if we are going to stick with 5.11, or since things are close, do the 5.12-rc7 to final bump during the freeze? The reason I'm asking is that the 5.12 kernel has the kernel interfaces which power-profile-daemon: https://gitlab.gnome.org/Teams/Design/settings-mockups/-/blob/master/power/… http://www.hadess.net/2020/09/power-profiles-daemon-new-project.html Will use to set the performance (aka platform) profile on for example ThinkPad laptops. So if we are going to ship with 5.12, then everything will be great, but if we are going to go with 5.11, then I should probably backport the necessary bits to the Fedora 5.11 kernels (the patches are not that big, it just took a while for everyone to agree on the userspace API). So, what kernel-version are we planning on shipping F34 gold with? Regards, Hans

2 5

Re: Kernel version plans for Fedora 34 ?
by Justin Forbes 12 Feb '21

12 Feb '21

On Thu, Feb 11, 2021 at 1:01 PM Bastien Nocera <hadess(a)hadess.net> wrote: > > On Thu, 2021-02-11 at 19:32 +0100, Hans de Goede wrote: > <snip> > > So where do I submit these once backported ? Do I just add them to > > dist-git > > as before ? AFAIK 5.11 will be the first kernel-ark based Fedora > > kernel > > (at least 5.10 dist-git does not look ark based), right ? > > I recently wanted to do that for a Bluetooth patch, and this is how I > went about it, along with discussions that happened on the list: > https://gitlab.com/cki-project/kernel-ark/-/merge_requests/872 > > I don't know whether I would have needed to proceed to get this > particular patch into stable releases, like Fedora 33 though. > The Fedora stable branches are a bit different, in that they do not copy over to ELN, so it is a much less formal process. Basically either I take it or I don't. And that is typically determined by a) What is the upstream status? b) How invasive is the backport? c) What is it trying to solve? Justin

1 0

[OS-BUILD PATCH] [redhat] New configs in drivers/perf
by GitLab Bridge on behalf of redhat-patchlab 11 Feb '21

11 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_ARM_DMC620_PMU: Support for PMU events monitoring on the ARM DMC-620 memory controller. Symbol: ARM_DMC620_PMU [=n] Type : tristate Defined at drivers/perf/Kconfig:133 Prompt: Enable PMU support for the ARM DMC-620 memory controller Depends on: PERF_EVENTS [=y] && (ARM64 [=y] && ACPI [=y] || COMPILE_TEST [=n]) Location: -> Device Drivers -> Performance monitor support --- Cc: Mark Salter <msalter(a)redhat.com> Cc: Mark Langsdorf <mlangsdo(a)redhat.com> Cc: Jeremy Linton <jlinton(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_ARM_DMC620_PMU | 1 + .../generic/CONFIG_ARM_DMC620_PMU | 17 ----------------- 2 files changed, 1 insertion(+), 17 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_ARM_DMC620_PMU delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ARM_DMC620_PMU diff --git a/redhat/configs/common/generic/CONFIG_ARM_DMC620_PMU b/redhat/configs/common/generic/CONFIG_ARM_DMC620_PMU new file mode 100644 index 000000000000..a7163f24fe2d --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_ARM_DMC620_PMU @@ -0,0 +1 @@ +# CONFIG_ARM_DMC620_PMU is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_ARM_DMC620_PMU b/redhat/configs/pending-common/generic/CONFIG_ARM_DMC620_PMU deleted file mode 100644 index a086d46317e9..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_ARM_DMC620_PMU +++ /dev/null @@ -1,17 +0,0 @@ -# CONFIG_ARM_DMC620_PMU: -# -# Support for PMU events monitoring on the ARM DMC-620 memory -# controller. -# -# Symbol: ARM_DMC620_PMU [=n] -# Type : tristate -# Defined at drivers/perf/Kconfig:133 -# Prompt: Enable PMU support for the ARM DMC-620 memory controller -# Depends on: PERF_EVENTS [=y] && (ARM64 [=y] && ACPI [=y] || COMPILE_TEST [=n]) -# Location: -# -> Device Drivers -# -> Performance monitor support -# -# -# -# CONFIG_ARM_DMC620_PMU is not set -- GitLab

3 3

Latest 5.11 kernels are only build for rawhide/F35, not available for F34
by Hans de Goede 11 Feb '21

11 Feb '21

Hi Justin, F34 has branched, so now, e.g. this kernel: https://koji.fedoraproject.org/koji/buildinfo?buildID=1706039 Only has a fc35 tag and there is no kernel-5.11.0-0.rc7.20210210gite0756cfc7d7c.150 pkg with a fc34 tag. So I think we need a separate F34 build for this kernel, or at least for the next kernel. Regards, Hans

3 3

Re: Ars claims: Fedora 32 is sluggish
by Ondrej Mosnacek 11 Feb '21

11 Feb '21

On Thu, Feb 11, 2021 at 10:14 AM Viktor Ashirov <vashirov(a)redhat.com> wrote: > On Wed, Feb 3, 2021 at 5:54 PM Michael Catanzaro <mcatanzaro(a)gnome.org> wrote: >> >> Hi, >> >> Has anybody investigated Jim Salter's claims that Fedora 32 is slow to >> launch applications? Recent article: >> >> https://arstechnica.com/gadgets/2021/02/ubuntu-core-20-adds-secure-boot-wit… >> >> "in my experience, Fedora 32 is noticeably, demonstrably more sluggish >> to launch applications than Ubuntu is in general." >> >> Original article: >> >> https://arstechnica.com/gadgets/2020/05/linux-distro-review-fedora-workstat… >> >> Would be good to know, for starters, whether this difference is real >> and measurable. > > This was bugging me for a while. I also noticed that Fedora 32 is a bit slower than it used to be. Compilation time of a project that I'm working on went from ~35-36 seconds to ~47-48. At first I thought that it's just another round of CPU vulnerabilities mitigations that introduced a performance drop. But after some digging I found that the default CPU governor was switched from 'ondemand' to 'schedutil' in Fedora kernel 5.9.7: > https://src.fedoraproject.org/rpms/kernel/c/73c86ebaee23df8310b903c1dab2176… > (see configs/fedora/generic/CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL) > > I switched it back using cpupower from kernel-tools: > $ sudo cpupower frequency-set --governor ondemand > > And confirmed that my compilation time went back to the previous ~35 seconds. > In the end I switched the governor to 'performance' and shaved another 5 seconds. And gnome-shell no longer feels sluggish, switching tabs in the browser is also instant. > To make the change permanent I used settings in /etc/sysconfig/cpupower and enabled cpupower service: > $ sudo systemctl enable --now cpupower.service > > The change of the default CPU governor looks pretty significant to me, but I couldn't find any discussions about it. CCing the Fedora kernel list and Justin. At the ARK tree level, the change was introduced in this commit, with no explanation: https://gitlab.com/cki-project/kernel-ark/commit/9d69ad49ab90db607e25a99eac… Justin, do you remember the reason for the change? Can/should it be reverted? -- Ondrej Mosnacek Software Engineer, Linux Security - SELinux kernel Red Hat, Inc.

3 2

✅ PASS: Test report for kernel 5.10.15-200.fc33 (fedora-33)
by CKI Project 11 Feb '21

11 Feb '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.10.15-200.fc33 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=61719970 The results of these automated tests are provided below. Overall result: PASSED Tests: OK All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng ppc64le: Host 1: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test s390x: Host 1: ✅ Boot test 🚧 ✅ Storage blktests 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng Host 2: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity x86_64: Host 1: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ xfstests - nfsv4.2 🚧 ❌ xfstests - cifsv3.11 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng Host 2: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

Self Introduction
by socrates bonomar 11 Feb '21

11 Feb '21

Hi, I'm from Southeast Africa, specifically Mozambique, last year I finished the study with BLFS, and I feel ready to support you in the development of this magnificent operating system. I have no problem handling unix tools, writing shell scripts (I like zsh), programming in C/C ++ among other things. I look forward to working with you for long periods of time.

1 0

[OS-BUILD PATCH] process_configs.sh: fix find/xargs data flow
by Ondrej Mosnáček (via Email Bridge) 11 Feb '21

11 Feb '21

From: Ondrej Mosnacek <omosnace(a)redhat.com> process_configs.sh: fix find/xargs data flow `xargs -0` expects arguments delimited by \0 on stdin, but instead it recieves a list of filenames delimited by \n from `find`. Fix that by adding `-print0` to `find` so that it outputs the filenames delimited by \0 as xargs expects. Signed-off-by: Ondrej Mosnacek <omosnace(a)redhat.com> diff a/redhat/configs/process_configs.sh b/redhat/configs/process_configs.sh --- a/redhat/configs/process_configs.sh +++ b/redhat/configs/process_configs.sh @@ -79,7 +79,7 @@ checkoptions() then while read -r LINE do - if find ./ -name "$(echo "$LINE" | awk -F "=" ' { print $1 } ' | awk ' { print $2 }')" | xargs -0 grep ^ | grep -q "process_configs_known_broken"; then + if find ./ -name "$(echo "$LINE" | awk -F "=" ' { print $1 } ' | awk ' { print $2 }')" -print0 | xargs -0 grep ^ | grep -q "process_configs_known_broken"; then # This is a known broken config. # See script help warning. checkoptions_error=false -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/885

2 5

[OS-BUILD PATCH] test, please ignore
by Don Zickus (via Email Bridge) 10 Feb '21

10 Feb '21

From: Don Zickus <dzickus(a)redhat.com> test, please ignore diff a/redhat/Makefile b/redhat/Makefile --- a/redhat/Makefile +++ b/redhat/Makefile @@ -1,4 +1,5 @@ GIT ?= git +# testing comment include Makefile.common include Makefile.rhpkg -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/892

1 0

[OS-BUILD PATCH 0/2] RHMAINTAINERS: Update for 20210209
by Prarit Bhargava (via Email Bridge) 10 Feb '21

10 Feb '21

From: Prarit Bhargava on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/890 Update for Feb 9 2021 Changes: 288cb5bb5524 (Waiman Long) RHMAINTAINERS: Add futex subsystem 6aa5c8637fd2 (Marcelo Ricardo Leitner) RHMAINTAINERS: NETWORKING: Add entry for Balazs Nemeth redhat/rhdocs/MAINTAINERS/RHMAINTAINERS | 12 ++++++++++++ 1 file changed, 12 insertions(+)

3 4

[OS-BUILD PATCH 0/4] Patch + Kconfig changes to prefer the SOF driver on Intel LPE audio hardware
by Hans de Goede (via Email Bridge) 10 Feb '21

10 Feb '21

From: Hans de Goede on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/889 This merge-req implements: https://fedoraproject.org/w/index.php?title=Changes/SofDefaultForIntelLp e It consists of 4 patches: 1. A patch making the preferred driver selectable in Kconfig, which is [already in -next](https://git.kernel.org/pub/scm/linux/kernel/git/tiwai /sound.git/commit/?h=for- next&id=5427c7d6296ee574037c4a6649ac45a9474d1f13) 2. Automatic creation of redhat/configs/pending-*/generic/CONFIG_SND_INTEL_BYT_PREFER_SOF files 3. Move the fedora CONFIG_SND_INTEL_BYT_PREFER_SOF config out of pending and enable it 4. Add a redhat/rebase-notes.txt with a reminder that on Fedora kernel rebases it should be disabled for F33 and older. Note I've left the rhel config for this in pending-rhel, leaving the decision of what to do with this up to the RHEL kernel folks. I believe that it makes sense to also enable this for RHEL. Intel LPE audio hardware is used in POS systems which are supported by RHEL and the SST driver will not be maintained anymore going forward, so for RHEL9 it is probably better to switch to the SOF driver which will actually see ongoing maintenance work upstream.

2 24

[OS-BUILD PATCH] RHMAINTAINERS: Fix list entries for kernel-patches@redhat.com
by Prarit Bhargava (via Email Bridge) 09 Feb '21

09 Feb '21

From: Prarit Bhargava <prarit(a)redhat.com> RHMAINTAINERS: Fix list entries for kernel-patches(a)redhat.com kernel-patches(a)redhat.com is a list, not a maintainer. Signed-off-by: Prarit Bhargava <prarit(a)redhat.com> diff a/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS b/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS --- a/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS +++ b/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS @@ -284,7 +284,7 @@ ARCHITECTURE DIRECTORY FILES M: Prarit Bhargava <prarit(a)redhat.com> M: David Arcari <darcari(a)redhat.com> M: Mark Salter <msalter(a)redhat.com> -M: kernel-patches(a)redhat.com +L: kernel-patches(a)redhat.com F: arch/Kconfig ARM64 PORT (AARCH64 ARCHITECTURE) @@ -1490,7 +1490,7 @@ F: include/linux/psci.h F: include/uapi/linux/psci.h POWERPC (64-BIT) -M: kernel-patches(a)redhat.com +L: kernel-patches(a)redhat.com S: Maintained F: arch/powerpc/ @@ -1983,13 +1983,13 @@ F: Documentation/filesystems/xfs.txt F: fs/xfs/ ZBUD COMPRESSED PAGE ALLOCATOR -M: kernel-patches(a)redhat.com +L: kernel-patches(a)redhat.com S: Maintained F: mm/zbud.c F: include/linux/zbud.h ZSWAP COMPRESSED SWAP CACHING -M: kernel-patches(a)redhat.com +L: kernel-patches(a)redhat.com S: Maintained F: mm/zswap.c -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/891

2 1

[OS-BUILD PATCH] [redhat] spec: package decompressor vmlinux for s390
by Philipp Rudo (via Email Bridge) 09 Feb '21

09 Feb '21

From: Philipp Rudo <prudo(a)linux.ibm.com> [redhat] spec: package decompressor vmlinux for s390 On s390 more and more code from the early boot stage is moved to the decompressor. With this the code complexity and thus the chances to introduce bugs increases. In order to be able to debug these early boot bugs package the decompressors vmlinux together with the other debuginfo for s390. This change requires kernel commit 7a84ffc0471f ("s390/boot: add build-id to decompressor") to work. Upstream Status: RHEL only Signed-off-by: Philipp Rudo <prudo(a)linux.ibm.com> diff a/redhat/kernel.spec.template b/redhat/kernel.spec.template --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -396,6 +396,7 @@ Summary: The Linux kernel %define hdrarch s390 %define all_arch_configs kernel-%{version}-s390x.config %define kernel_image arch/s390/boot/bzImage +%define vmlinux_decompressor arch/s390/boot/compressed/vmlinux %endif %ifarch %{arm} @@ -1796,6 +1797,16 @@ BuildKernel() { # mkdir -p $RPM_BUILD_ROOT%{debuginfodir}/lib/modules/$KernelVer cp vmlinux $RPM_BUILD_ROOT%{debuginfodir}/lib/modules/$KernelVer + if [ -n "%{vmlinux_decompressor}" ]; then + eu-readelf -n %{vmlinux_decompressor} | grep "Build ID" | awk '{print $NF}' > vmlinux.decompressor.id + # Without build-id the build will fail. But for s390 the build-id + # wasn't added before 5.11. In case it is missing prefer not + # packaging the debuginfo over a build failure. + if [ -s vmlinux.decompressor.id ]; then + cp vmlinux.decompressor.id $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/vmlinux.decompressor.id + cp %{vmlinux_decompressor} $RPM_BUILD_ROOT%{debuginfodir}/lib/modules/$KernelVer/vmlinux.decompressor + fi + fi %endif find $RPM_BUILD_ROOT/lib/modules/$KernelVer -name "*.ko" -type f >modnames -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/883

4 151

[OS-BUILD PATCH] CI: Drop MR ID from the name variable
by Veronika Kabátová (via Email Bridge) 09 Feb '21

09 Feb '21

From: Veronika Kabatova <vkabatov(a)redhat.com> CI: Drop MR ID from the name variable While this is not breaking ARK testing as the pipeline is not fully building the kernel but only SRPM, we should fix this repo as well to not run into any suprises in the future. The name is used to grab the correct ccache file, and using the MR ID in there would render the whole ccache setup useless. Signed-off-by: Veronika Kabatova <vkabatov(a)redhat.com> diff a/.gitlab-ci.yml b/.gitlab-ci.yml --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -24,7 +24,7 @@ trigger_pipeline: mr_id: ${CI_MERGE_REQUEST_IID} mr_url: ${CI_MERGE_REQUEST_PROJECT_URL}/-/merge_requests/${CI_MERGE_REQUEST_IID} title: ${CI_COMMIT_TITLE} - name: kernel-ark-${CI_MERGE_REQUEST_ID} + name: kernel-ark # We only need srpm so skip the rest of the stages kernel_type: upstream -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/888

2 75

✅ PASS: Test report for kernel 5.10.14-200.fc33 (fedora-33)
by CKI Project 09 Feb '21

09 Feb '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.10.14-200.fc33 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=61541770 The results of these automated tests are provided below. Overall result: PASSED Tests: OK All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng Host 2: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity ppc64le: Host 1: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test s390x: Host 1: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test 🚧 ✅ Storage blktests 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng x86_64: Host 1: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ xfstests - nfsv4.2 🚧 ✅ xfstests - cifsv3.11 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

[OS-BUILD PATCH] redhat: add DUP and kpatch certificates to system trusted keys for RHEL build
by Herton Krzesinski (via Email Bridge) 08 Feb '21

08 Feb '21

From: Herton R. Krzesinski <herton(a)redhat.com> redhat: add DUP and kpatch certificates to system trusted keys for RHEL build We were not including yet the DUP and kpatch additional certificates in the build process for RHEL. Do it by creating the required pem file and setting the related kernel config option. Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com> diff a/redhat/kernel.spec.template b/redhat/kernel.spec.template --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -719,6 +719,9 @@ Source56: update_scripts.sh Source54: mod-internal.list +Source100: rheldup3.x509 +Source101: rhelkpatch1.x509 + Source200: check-kabi Source201: Module.kabi_aarch64 @@ -1323,6 +1326,18 @@ do done %endif +# Add DUP and kpatch certificates to system trusted keys for RHEL +%if 0%{?rhel} +%if %{signkernel}%{signmodules} +openssl x509 -inform der -in %{SOURCE100} -out rheldup3.pem +openssl x509 -inform der -in %{SOURCE101} -out rhelkpatch1.pem +cat rheldup3.pem rhelkpatch1.pem > ../certs/rhel.pem +for i in *.config; do + sed -i 's@CONFIG_SYSTEM_TRUSTED_KEYS=""@CONFIG_SYSTEM_TRUSTED_KEYS="certs/rhel.pem"@' $i +done +%endif +%endif + cp %{SOURCE52} . OPTS="" %if %{with_configchecks} -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/882

2 74

[OS-BUILD PATCH] fedora: minor arm sound config updates
by pbrobinson (via Email Bridge) 07 Feb '21

07 Feb '21

From: Peter Robinson <pbrobinson(a)redhat.com> fedora: minor arm sound config updates Signed-off-by: Peter Robinson <pbrobinson(a)redhat.com> diff a/redhat/configs/fedora/generic/arm/aarch64/CONFIG_SND_SOC_RK3328 b/redhat/configs/fedora/generic/arm/aarch64/CONFIG_SND_SOC_RK3328 --- /dev/null +++ b/redhat/configs/fedora/generic/arm/aarch64/CONFIG_SND_SOC_RK3328 @@ -0,0 +1 @@ +CONFIG_SND_SOC_RK3328=m diff a/redhat/configs/fedora/generic/arm/aarch64/CONFIG_SND_SOC_RT5659 b/redhat/configs/fedora/generic/arm/aarch64/CONFIG_SND_SOC_RT5659 --- /dev/null +++ b/redhat/configs/fedora/generic/arm/aarch64/CONFIG_SND_SOC_RT5659 @@ -0,0 +1 @@ +CONFIG_SND_SOC_RT5659=m -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/887

1 0

Adding a patch to the Fedora kernels for F34 and later only ?
by Hans de Goede 06 Feb '21

06 Feb '21

Hi All, With new kernel-ark flow, it is not entirely clear to me how to do $subject ? In the past I would just add the patch to dist-git with a comment that it is only for F34+, but with ARK the dist-git content seems to be more or less auto-generated from kernel-ark.git. I need to add a small patch to the Fedora kernels for: https://fedoraproject.org/w/index.php?title=Changes/SofDefaultForIntelLpe The default driver is selected based on the order of a couple of entries in an array, so I need to swap that order. I can either just hardcode the order, or I can add a Kconfig for this, if having different Kconfig settings is easier between releases, so 2 questions: 1. Should the patch just hardcode the new order or is a Kconfig option preferred (for the Fedora kernel workflow). 2. How do I get a patch *or* a Kconfig option added/set to/for the Fedora kernels with the patch/option only being applied to F34+ kernel builds ? Regards, Hans

2 2

[OS-BUILD PATCH] Update CKI pipeline project
by Veronika Kabátová (via Email Bridge) 05 Feb '21

05 Feb '21

From: Veronika Kabatova <vkabatov(a)redhat.com> Update CKI pipeline project The paths have been changed and CI won't work without this update. Signed-off-by: Veronika Kabatova <vkabatov(a)redhat.com> diff a/.gitlab-ci.yml b/.gitlab-ci.yml --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -37,7 +37,7 @@ trigger_pipeline: skip_test: 'true' trigger: - project: redhat/red-hat-ci-tools/kernel/cki-runs/trusted-pipelines + project: redhat/red-hat-ci-tools/kernel/cki-internal-pipelines/cki-trusted-contributors branch: kernel-ark strategy: depend -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/886

3 18

✅ PASS: Test report for kernel 5.10.13-200.fc33 (fedora-33)
by CKI Project 05 Feb '21

05 Feb '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.10.13-200.fc33 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=61305001 The results of these automated tests are provided below. Overall result: PASSED Tests: OK All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test ✅ stress: stress-ng 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test ppc64le: Host 1: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ LTP ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) 🚧 ⚡⚡⚡ CIFS Connectathon 🚧 ⚡⚡⚡ Ethernet drivers sanity Host 2: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test 🚧 ⚡⚡⚡ xfstests - ext4 🚧 ⚡⚡⚡ xfstests - xfs 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ Storage blktests 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage nvme - tcp 🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test Host 3: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ LTP ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) 🚧 ⚡⚡⚡ CIFS Connectathon 🚧 ⚡⚡⚡ Ethernet drivers sanity Host 4: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ LTP ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) 🚧 ⚡⚡⚡ CIFS Connectathon 🚧 ⚡⚡⚡ Ethernet drivers sanity s390x: Host 1: ✅ Boot test ✅ stress: stress-ng 🚧 ✅ Storage blktests 🚧 ❌ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test Host 2: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 3: ✅ Boot test ✅ kdump - sysrq-c x86_64: Host 1: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ ACPI table test ⚡⚡⚡ LTP ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) 🚧 ⚡⚡⚡ CIFS Connectathon 🚧 ⚡⚡⚡ Ethernet drivers sanity Host 2: ✅ Boot test ✅ stress: stress-ng 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ xfstests - nfsv4.2 🚧 ✅ xfstests - cifsv3.11 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test Host 3: ✅ Boot test 🚧 ✅ kdump - sysrq-c Host 4: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ ACPI table test ⚡⚡⚡ LTP ⚡⚡⚡ Loopdev Sanity ⚡⚡⚡ Memory: fork_mem ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) 🚧 ⚡⚡⚡ CIFS Connectathon 🚧 ⚡⚡⚡ Ethernet drivers sanity Host 5: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

[OS-BUILD PATCH] Rename the master branch to rawhide for Fedora
by Justin Forbes (via Email Bridge) 04 Feb '21

04 Feb '21

From: Justin M. Forbes <jforbes(a)fedoraproject.org> Rename the master branch to rawhide for Fedora Yesterday, dist-git in Fedora was change, renaming the master branch to either rawhide or main depending on the context. In our case, rawhide is the correct default branch going forward. You can not run 'make dist-git' successfully until this is merged. Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org> diff a/redhat/Makefile.common b/redhat/Makefile.common --- a/redhat/Makefile.common +++ b/redhat/Makefile.common @@ -140,7 +140,7 @@ CHANGELOG_PREV:=$(PACKAGE_NAME).changelog-$(RHEL_MAJOR).$(shell expr $(RHEL_MINO ifeq ("$(DIST)", ".elrdy") RHPRODUCT:=rhel-ready else ifeq ("$(IS_FEDORA)", "1") - RHPRODUCT:=master + RHPRODUCT:=rawhide else RHPRODUCT:=rhel-$(RHEL_MAJOR).$(RHEL_MINOR).0 endif -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/881

2 3

[OS-BUILD PATCH] Makefile targets for packit integration
by Ben Crocker (via Email Bridge) 03 Feb '21

03 Feb '21

From: Ben Crocker <bcrocker(a)redhat.com> Makefile targets for packit integration * dist-tarball * dist-kernelrelease * dist-kernelversion * dist-specfile dist-tarball echoes the path to the tarball, starting with redhat/. dist-kernelrelease echoes the kernel release string; dist-kernelversion echoes a full version string, and is meant to provide a finer granularity than dist-kernelrelease. dist-specfile (possibly) invokes setup-source, then echoes a path to the (possibly newly-generated) specfile. Signed-off-by: Ben Crocker <bcrocker(a)redhat.com> diff a/redhat/Makefile b/redhat/Makefile --- a/redhat/Makefile +++ b/redhat/Makefile @@ -200,6 +200,18 @@ $(KABIDW_TARBALL): @(cd kabi-dwarf && tar cjf $(SOURCES)/$(KABIDW_TARFILE) base run_kabi-dw.sh) +dist-tarball: $(TARBALL) + @echo "redhat/$(TARFILE)" + +dist-kernelrelease: + @echo $(PACKAGE_NAME)-$(KVERSION)-$(BUILD) + +dist-kernelversion: + @echo $(PACKAGE_NAME)-$(KVERSION)-$(DISTRO_BUILD) + +dist-specfile: setup-source + @echo $(SOURCES)/$(SPECFILE) + dist-git-version-check: @# genspec.sh uses pathspec magic that wasn't introduced until version 2.13 @IFS=" ."; \ -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/800

2 5

[OS-BUILD PATCH 0/2] Replace current awk logic in genspec.sh with a python script
by Herton Krzesinski (via Email Bridge) 03 Feb '21

03 Feb '21

From: Herton Krzesinski on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/865 The current awk logic is complex and relied on Patchwork metadata. As we moved on to gitlab, it doesn't pick anymore bugzilla or CVE info from commits. This adds a simpler python script which can scan through the commit log and adds bugzilla/cve info if available.

2 16

[OS-BUILD PATCH] kernel.spec.template - fix use_vdso usage
by Ben Crocker (via Email Bridge) 02 Feb '21

02 Feb '21

From: Ben Crocker <bcrocker(a)redhat.com> kernel.spec.template - fix use_vdso usage Signed-off-by: Ben Crocker <bcrocker(a)redhat.com> diff a/redhat/kernel.spec.template b/redhat/kernel.spec.template --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -466,7 +466,7 @@ Summary: The Linux kernel %define cpupowerarchs i686 x86_64 ppc64le aarch64 %endif -%if %{use_vdso} +%if 0%{?use_vdso} %if 0%{?skip_nonpae_vdso} %define _use_vdso 0 -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/879

2 5

[OS-BUILD PATCH] Remove deprecated Intel MIC config options
by GitLab Bridge on behalf of pbrobinson 02 Feb '21

02 Feb '21

From: Peter Robinson <pbrobinson(a)redhat.com> The Intel MIC drivers were removed in 5.10, in commit 80ade22, so these driver configs are now irrelvent so remove them. This primarilly affects Fedora as they were disabled in ARK anyway. Signed-off-by: Peter Robinson <pbrobinson(a)redhat.com> --- redhat/configs/ark/generic/CONFIG_INTEL_MIC_BUS | 1 - redhat/configs/ark/generic/CONFIG_SCIF_BUS | 1 - redhat/configs/common/generic/CONFIG_VOP_BUS | 1 - redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_BUS | 1 - redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_CARD | 1 - redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_HOST | 1 - .../configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_X100_DMA | 1 - redhat/configs/fedora/generic/x86/x86_64/CONFIG_MIC_COSM | 1 - redhat/configs/fedora/generic/x86/x86_64/CONFIG_SCIF | 1 - redhat/configs/fedora/generic/x86/x86_64/CONFIG_SCIF_BUS | 1 - redhat/configs/fedora/generic/x86/x86_64/CONFIG_VOP | 1 - redhat/configs/fedora/generic/x86/x86_64/CONFIG_VOP_BUS | 1 - 12 files changed, 12 deletions(-) delete mode 100644 redhat/configs/ark/generic/CONFIG_INTEL_MIC_BUS delete mode 100644 redhat/configs/ark/generic/CONFIG_SCIF_BUS delete mode 100644 redhat/configs/common/generic/CONFIG_VOP_BUS delete mode 100644 redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_BUS delete mode 100644 redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_CARD delete mode 100644 redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_HOST delete mode 100644 redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_X100_DMA delete mode 100644 redhat/configs/fedora/generic/x86/x86_64/CONFIG_MIC_COSM delete mode 100644 redhat/configs/fedora/generic/x86/x86_64/CONFIG_SCIF delete mode 100644 redhat/configs/fedora/generic/x86/x86_64/CONFIG_SCIF_BUS delete mode 100644 redhat/configs/fedora/generic/x86/x86_64/CONFIG_VOP delete mode 100644 redhat/configs/fedora/generic/x86/x86_64/CONFIG_VOP_BUS diff --git a/redhat/configs/ark/generic/CONFIG_INTEL_MIC_BUS b/redhat/configs/ark/generic/CONFIG_INTEL_MIC_BUS deleted file mode 100644 index 0939473b1553..000000000000 --- a/redhat/configs/ark/generic/CONFIG_INTEL_MIC_BUS +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_INTEL_MIC_BUS is not set diff --git a/redhat/configs/ark/generic/CONFIG_SCIF_BUS b/redhat/configs/ark/generic/CONFIG_SCIF_BUS deleted file mode 100644 index d6a88748b388..000000000000 --- a/redhat/configs/ark/generic/CONFIG_SCIF_BUS +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_SCIF_BUS is not set diff --git a/redhat/configs/common/generic/CONFIG_VOP_BUS b/redhat/configs/common/generic/CONFIG_VOP_BUS deleted file mode 100644 index 111a702b5999..000000000000 --- a/redhat/configs/common/generic/CONFIG_VOP_BUS +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_VOP_BUS is not set diff --git a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_BUS b/redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_BUS deleted file mode 100644 index 0d018fbf4fd8..000000000000 --- a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_BUS +++ /dev/null @@ -1 +0,0 @@ -CONFIG_INTEL_MIC_BUS=m diff --git a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_CARD b/redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_CARD deleted file mode 100644 index ce7cbb77ade3..000000000000 --- a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_CARD +++ /dev/null @@ -1 +0,0 @@ -CONFIG_INTEL_MIC_CARD=m diff --git a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_HOST b/redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_HOST deleted file mode 100644 index 26e9b3ccff00..000000000000 --- a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_HOST +++ /dev/null @@ -1 +0,0 @@ -CONFIG_INTEL_MIC_HOST=m diff --git a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_X100_DMA b/redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_X100_DMA deleted file mode 100644 index df573d1ab0a7..000000000000 --- a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_INTEL_MIC_X100_DMA +++ /dev/null @@ -1 +0,0 @@ -CONFIG_INTEL_MIC_X100_DMA=m diff --git a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_MIC_COSM b/redhat/configs/fedora/generic/x86/x86_64/CONFIG_MIC_COSM deleted file mode 100644 index 826edffcdc91..000000000000 --- a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_MIC_COSM +++ /dev/null @@ -1 +0,0 @@ -CONFIG_MIC_COSM=m diff --git a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_SCIF b/redhat/configs/fedora/generic/x86/x86_64/CONFIG_SCIF deleted file mode 100644 index 74fab518255e..000000000000 --- a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_SCIF +++ /dev/null @@ -1 +0,0 @@ -CONFIG_SCIF=m diff --git a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_SCIF_BUS b/redhat/configs/fedora/generic/x86/x86_64/CONFIG_SCIF_BUS deleted file mode 100644 index 054e08ed2f57..000000000000 --- a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_SCIF_BUS +++ /dev/null @@ -1 +0,0 @@ -CONFIG_SCIF_BUS=m diff --git a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_VOP b/redhat/configs/fedora/generic/x86/x86_64/CONFIG_VOP deleted file mode 100644 index 3f6192e2b20e..000000000000 --- a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_VOP +++ /dev/null @@ -1 +0,0 @@ -CONFIG_VOP=m diff --git a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_VOP_BUS b/redhat/configs/fedora/generic/x86/x86_64/CONFIG_VOP_BUS deleted file mode 100644 index 83c12391bd88..000000000000 --- a/redhat/configs/fedora/generic/x86/x86_64/CONFIG_VOP_BUS +++ /dev/null @@ -1 +0,0 @@ -CONFIG_VOP_BUS=m -- GitLab

2 3

[OS-BUILD PATCH] Remove bpf-helpers.7 from bpftool package
by Jiri Olsa (via Email Bridge) 02 Feb '21

02 Feb '21

From: Jiri Olsa <jolsa(a)kernel.org> Remove bpf-helpers.7 from bpftool package It's packaged by man-pages. Removing bpf-helpers.7 from bpftool package (rhbz #1686954, #1918707). Signed-off-by: Jiri Olsa <jolsa(a)redhat.com> diff a/redhat/kernel.spec.template b/redhat/kernel.spec.template --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -2295,6 +2295,8 @@ popd pushd tools/bpf/bpftool %{bpftool_make} prefix=%{_prefix} bash_compdir=%{_sysconfdir}/bash_completion.d/ mandir=%{_mandir} install doc-install popd +# man-pages packages this (rhbz #1686954, #1918707) +rm %{buildroot}%{_mandir}/man7/bpf-helpers.7 %endif %if %{with_selftests} @@ -2621,7 +2623,6 @@ fi %{_mandir}/man8/bpftool-prog.8.gz %{_mandir}/man8/bpftool-perf.8.gz %{_mandir}/man8/bpftool.8.gz -%{_mandir}/man7/bpf-helpers.7.gz %{_mandir}/man8/bpftool-net.8.gz %{_mandir}/man8/bpftool-feature.8.gz %{_mandir}/man8/bpftool-btf.8.gz -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/876

2 12

[OS-BUILD PATCH] [redhat] New configs in security/keys
by GitLab Bridge on behalf of jeremycline 02 Feb '21

02 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- redhat/configs/common/generic/CONFIG_KEY_NOTIFICATIONS | 0 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_KEY_NOTIFICATIONS diff --git a/redhat/configs/common/generic/CONFIG_KEY_NOTIFICATIONS b/redhat/configs/common/generic/CONFIG_KEY_NOTIFICATIONS new file mode 100644 index 000000000000..e69de29bb2d1 -- GitLab

6 8

kernel 5.10.11 overwrote my private UEFI key
by stan 01 Feb '21

01 Feb '21

Hi, I compile a custom kernel from the Fedora src.rpm. When I compiled the 5.10.11 kernel, it overwrote my private key when I installed it. The last 5.10 kernel I compiled and installed, 5.10.4, did not. I don't expect any kind of fix since it is a custom compile, just putting this out there as a data point in case anyone else runs into this and is scratching their head.

1 0

✅ PASS: Test report for kernel 5.10.12-200.fc33 (fedora-33)
by CKI Project 01 Feb '21

01 Feb '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.10.12-200.fc33 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=60999816 The results of these automated tests are provided below. Overall result: PASSED Tests: OK All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test ✅ stress: stress-ng 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test ppc64le: Host 1: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test Host 2: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity s390x: Host 1: ✅ Boot test ✅ stress: stress-ng 🚧 ✅ Storage blktests 🚧 ❌ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test Host 2: ✅ Boot test ✅ kdump - sysrq-c Host 3: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity x86_64: Host 1: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ stress: stress-ng 🚧 ⚡⚡⚡ xfstests - ext4 🚧 ⚡⚡⚡ xfstests - xfs 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - nfsv4.2 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage nvme - tcp 🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test Host 2: ✅ Boot test 🚧 ✅ kdump - sysrq-c Host 3: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 4: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test ⚡⚡⚡ stress: stress-ng 🚧 ⚡⚡⚡ xfstests - ext4 🚧 ⚡⚡⚡ xfstests - xfs 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - nfsv4.2 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage nvme - tcp 🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test Host 5: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test ✅ stress: stress-ng 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ xfstests - nfsv4.2 🚧 ✅ xfstests - cifsv3.11 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage nvme - tcp 🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

[OS-BUILD PATCH] [redhat] Makefile: new dist-buildreq-check target
by Ben Crocker (via Email Bridge) 01 Feb '21

01 Feb '21

From: Ben Crocker <bcrocker(a)redhat.com> [redhat] Makefile: new dist-buildreq-check target Add a new dist-buildreq-check target that checks for missing packages via rpmspec -q --buildrequires, and make dist-configs-prep dependent on it. This change is based on suggestions from Josh Poimboeuf, Don Zickus, and Herton Krzesinski. Ultimately this is Herton's version, which generates the list of missing packages from an already-created kernel.spec file. Signed-off-by: Ben Crocker <bcrocker(a)redhat.com> diff a/redhat/Makefile b/redhat/Makefile --- a/redhat/Makefile +++ b/redhat/Makefile @@ -144,7 +144,7 @@ rh-configs: dist-configs dist-configs-check: dist-configs-prep cd $(REDHAT)/configs; ./process_configs.sh $(PROCESS_CONFIGS_CHECK_OPTS) $(PACKAGE_NAME) -dist-configs-prep: dist-clean-configs +dist-configs-prep: dist-clean-configs dist-buildreq-check cd $(REDHAT)/configs; ./build_configs.sh "$(PACKAGE_NAME)" "$(ARCH_MACH)" "$(FLAVOR)" dist-configs-arch: ARCH_MACH = $(MACH) @@ -210,6 +210,17 @@ dist-git-version-check: exit 1; \ fi +dist-buildreq-check: setup-source + @PKGLIST="rpm-build $(rpmspec -q --buildrequires $(SOURCES)/$(SPECFILE) | cut -d ' ' -f 1)"; \ + MISSING=""; \ + for pkg in $$PKGLIST; do \ + rpm -q --whatprovides $$pkg >/dev/null || MISSING="$$MISSING $$pkg"; \ + done; \ + if [ -n "$$MISSING" ]; then \ + echo "Error: please install $$MISSING"; \ + exit 1; \ + fi + setup-source: dist-git-version-check dist-clean-sources @cp $(REDHAT)/$(SPECFILE).template $(SOURCES)/$(SPECFILE) @if [ ! -e $(REDHAT)/$(CHANGELOG) ]; then \ @@ -265,7 +276,7 @@ sources-rh: $(TARBALL) generate-testpatch-tmp fi @(cd kabi-dwarf && tar cjf $(SOURCES)/$(KABIDW_TARFILE) base run_kabi-dw.sh) -dist-sources: setup-source dist-configs-check dist-kabi dist-kabi-dup sources-rh +dist-sources: dist-configs-check dist-kabi dist-kabi-dup sources-rh dist-test-patch: generate-testpatch-tmp @mv $(TESTPATCH).tmp $(TESTPATCH); @@ -515,6 +526,7 @@ dist-full-help: @echo '' @echo 'Misc targets:' + @echo ' dist-buildreq-check - Checks for presence of packages required for build' @echo ' dist-get-latest - Returns the latest "known good" kernel from brew. This' @echo ' should not be confused with the latest top-of-tree' @echo ' development tag.' -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/859

2 7

[OS-BUILD PATCH] redhat: remove remaining references of CONFIG_RH_DISABLE_DEPRECATED
by Herton Krzesinski (via Email Bridge) 01 Feb '21

01 Feb '21

From: Herton R. Krzesinski <herton(a)redhat.com> redhat: remove remaining references of CONFIG_RH_DISABLE_DEPRECATED In the commit "Rename RH_DISABLE_DEPRECATED to RHEL_DIFFERENCES", the change in kernel/Makefile was an addition instead of a rename. This change fixes that by removing the old line still referencing CONFIG_RH_DISABLE_DEPRECATED. Also, the redhat/configs tree still have the old config option files, remove them too. Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com> diff a/kernel/Makefile b/kernel/Makefile --- a/kernel/Makefile +++ b/kernel/Makefile @@ -12,7 +12,6 @@ obj-y = fork.o exec_domain.o panic.o \ notifier.o ksysfs.o cred.o reboot.o \ async.o range.o smpboot.o ucount.o regset.o -obj-$(CONFIG_RH_DISABLE_DEPRECATED) += rh_taint.o obj-$(CONFIG_RHEL_DIFFERENCES) += rh_taint.o obj-$(CONFIG_USERMODE_DRIVER) += usermode_driver.o obj-$(CONFIG_MODULES) += kmod.o diff a/redhat/configs/ark/generic/CONFIG_RH_DISABLE_DEPRECATED b/redhat/configs/ark/generic/CONFIG_RH_DISABLE_DEPRECATED --- a/redhat/configs/ark/generic/CONFIG_RH_DISABLE_DEPRECATED +++ /dev/null @@ -1 +0,0 @@ -CONFIG_RH_DISABLE_DEPRECATED=y diff a/redhat/configs/fedora/generic/CONFIG_RH_DISABLE_DEPRECATED b/redhat/configs/fedora/generic/CONFIG_RH_DISABLE_DEPRECATED --- a/redhat/configs/fedora/generic/CONFIG_RH_DISABLE_DEPRECATED +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_RH_DISABLE_DEPRECATED is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/878

2 4

[OS-BUILD PATCH] .gitignore: fix previous mismerge with "HEAD line"
by Herton Krzesinski (via Email Bridge) 01 Feb '21

01 Feb '21

From: Herton R. Krzesinski <herton(a)redhat.com> .gitignore: fix previous mismerge with "HEAD line" The merge conflict marker "<<<<<<< HEAD" was left over from a previous merge. Remove it. Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com> diff a/.gitignore b/.gitignore --- a/.gitignore +++ b/.gitignore @@ -153,7 +153,6 @@ x509.genkey # Clang's compilation database file /compile_commands.json -<<<<<<< HEAD # # Red Hat # -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/877

2 4

[OS-BUILD PATCH] Turn off vdso_install for ppc
by GitLab Bridge on behalf of jmflinuxtx 01 Feb '21

01 Feb '21

From: "Justin M. Forbes" <jforbes(a)fedoraproject.org> With upstream commit 7fe2de246e21f01212a8923fbabb4ac84c944d4a powerpc/vdso: Stripped VDSO is not needed, don't build it the make targets for vdso_install are gone for ppc. If we call them, the build fails. This just turns them off. Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org> --- redhat/kernel.spec.template | 1 + 1 file changed, 1 insertion(+) diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template index 51e521c708d7..0638d9a7ca69 100755 --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -379,6 +379,7 @@ Summary: The Linux kernel %define make_target vmlinux %define kernel_image vmlinux %define kernel_image_elf 1 +%define use_vdso 0 %define all_arch_configs kernel-%{version}-ppc64le*.config %endif -- GitLab

6 11

[OS-BUILD PATCH] [redhat] New configs in drivers/leds
by CKI Gitlab (via Email Bridge) 01 Feb '21

01 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/leds Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_LEDS_RT8515: This option enables support for the Richtek RT8515 flash and torch LEDs found on some mobile phones. To compile this driver as a module, choose M here: the module will be called leds-rt8515. Symbol: LEDS_RT8515 [=n] Type : tristate Defined at drivers/leds/flash/Kconfig:5 Prompt: LED support for Richtek RT8515 flash/torch LED Depends on: NEW_LEDS [=y] && LEDS_CLASS_FLASH [=m] && GPIOLIB [=y] Location: -> Device Drivers -> LED Support (NEW_LEDS [=y]) --- Cc: Tony Camuso <tcamuso(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_LEDS_RT8515 b/redhat/configs/common/generic/CONFIG_LEDS_RT8515 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_LEDS_RT8515 @@ -0,0 +1 @@ +# CONFIG_LEDS_RT8515 is not set diff a/redhat/configs/pending-common/generic/CONFIG_LEDS_RT8515 b/redhat/configs/pending-common/generic/CONFIG_LEDS_RT8515 --- a/redhat/configs/pending-common/generic/CONFIG_LEDS_RT8515 +++ /dev/null @@ -1,20 +0,0 @@ -# CONFIG_LEDS_RT8515: -# -# This option enables support for the Richtek RT8515 flash -# and torch LEDs found on some mobile phones. -# -# To compile this driver as a module, choose M here: the module -# will be called leds-rt8515. -# -# Symbol: LEDS_RT8515 [=n] -# Type : tristate -# Defined at drivers/leds/flash/Kconfig:5 -# Prompt: LED support for Richtek RT8515 flash/torch LED -# Depends on: NEW_LEDS [=y] && LEDS_CLASS_FLASH [=m] && GPIOLIB [=y] -# Location: -# -> Device Drivers -# -> LED Support (NEW_LEDS [=y]) -# -# -# -# CONFIG_LEDS_RT8515 is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/880

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel February 2021