April 2021 - kernel - Fedora Mailing-Lists

[OS-BUILD PATCH] [redhat] New configs in drivers/power

by GitLab Bridge on behalf of jeremycline

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 years

3
2
0 / 0

[OS-BUILD PATCH] [redhat] New configs in drivers/nvmem

by CKI Gitlab (via Email Bridge)

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/nvmem 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_NVMEM_RMEM: This driver maps reserved memory into an nvmem device. It might be useful to expose information left by firmware in memory. This driver can also be built as a module. If so, the module will be called nvmem-rmem. Symbol: NVMEM_RMEM [=n] Type : tristate Defined at drivers/nvmem/Kconfig:273 Prompt: Reserved Memory Based Driver Support Depends on: NVMEM [=y] Location: -> Device Drivers -> NVMEM Support (NVMEM [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_NVMEM_RMEM b/redhat/configs/common/generic/CONFIG_NVMEM_RMEM --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_NVMEM_RMEM @@ -0,0 +1 @@ +# CONFIG_NVMEM_RMEM is not set diff a/redhat/configs/pending-common/generic/CONFIG_NVMEM_RMEM b/redhat/configs/pending-common/generic/CONFIG_NVMEM_RMEM --- a/redhat/configs/pending-common/generic/CONFIG_NVMEM_RMEM +++ /dev/null @@ -1,19 +0,0 @@ -# CONFIG_NVMEM_RMEM: -# -# This driver maps reserved memory into an nvmem device. It might be -# useful to expose information left by firmware in memory. -# -# This driver can also be built as a module. If so, the module -# will be called nvmem-rmem. -# Symbol: NVMEM_RMEM [=n] -# Type : tristate -# Defined at drivers/nvmem/Kconfig:273 -# Prompt: Reserved Memory Based Driver Support -# Depends on: NVMEM [=y] -# Location: -# -> Device Drivers -# -> NVMEM Support (NVMEM [=y]) -# -# -# -# CONFIG_NVMEM_RMEM is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/931

3 years

3
2
0 / 0

[OS-BUILD PATCH] [redhat] New configs in drivers/media

by CKI Gitlab (via Email Bridge)

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

3 years

2
1
0 / 0

[OS-BUILD PATCH] [redhat] New configs in crypto/Kconfig

by GitLab Bridge on behalf of jeremycline

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

3 years

13
21
0 / 0

[OS-BUILD PATCH] [redhat] New configs in drivers/net/can

by GitLab Bridge on behalf of jeremycline

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

3 years

4
5
0 / 0

[OS-BUILD PATCH] [redhat] New configs in arch/s390

by GitLab Bridge on behalf of redhat-patchlab

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 years

3
4
0 / 0

[OS-BUILD PATCH 0/2] enable CONFIG_CMA on x86_64 in ARK

by David Hildenbrand (via Email Bridge)

From: David Hildenbrand on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1023 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1945002 Enable CONFIG_CMA on x86_64 in ARK as we already have in fedora; CMA is Tech Preview in RHEL 9.

3 years

5
12
0 / 0

[OS-BUILD PATCH] [redhat] New configs in fs/fuse

by GitLab Bridge on behalf of jeremycline

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

3 years

4
4
0 / 0

[OS-BUILD PATCH] [redhat] New configs in drivers/ntb

by CKI Gitlab (via Email Bridge)

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/ntb 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_NTB_EPF: This driver supports EPF NTB on configurable endpoint. If unsure, say N. Symbol: NTB_EPF [=n] Type : tristate Defined at drivers/ntb/hw/epf/Kconfig:1 Prompt: Generic EPF Non-Transparent Bridge support Depends on: NTB [=m] && m && MODULES [=y] Location: -> Device Drivers -> Non-Transparent Bridge support (NTB [=m]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_NTB_EPF b/redhat/configs/common/generic/CONFIG_NTB_EPF --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_NTB_EPF @@ -0,0 +1 @@ +# CONFIG_NTB_EPF is not set diff a/redhat/configs/pending-common/generic/CONFIG_NTB_EPF b/redhat/configs/pending-common/generic/CONFIG_NTB_EPF --- a/redhat/configs/pending-common/generic/CONFIG_NTB_EPF +++ /dev/null @@ -1,17 +0,0 @@ -# CONFIG_NTB_EPF: -# -# This driver supports EPF NTB on configurable endpoint. -# If unsure, say N. -# -# Symbol: NTB_EPF [=n] -# Type : tristate -# Defined at drivers/ntb/hw/epf/Kconfig:1 -# Prompt: Generic EPF Non-Transparent Bridge support -# Depends on: NTB [=m] && m && MODULES [=y] -# Location: -# -> Device Drivers -# -> Non-Transparent Bridge support (NTB [=m]) -# -# -# -# CONFIG_NTB_EPF is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/930

3 years

2
1
0 / 0

[OS-BUILD PATCHv2 0/0] [redhat] New configs in drivers/cxl

by CKI Gitlab (via Email Bridge)

From: CKI Gitlab on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/927 NOTE: Truncated patchset due to missing @redhat.com email address on your GitLab profile at https://gitlab.com/-/profile. Once that is fixed, close and reopen the merge request to retrigger sending the emails. 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_CXL_BUS: CXL is a bus that is electrically compatible with PCI Express, but layers three protocols on that signalling (CXL.io, CXL.cache, and CXL.mem). The CXL.cache protocol allows devices to hold cachelines locally, the CXL.mem protocol allows devices to be fully coherent memory targets, the CXL.io protocol is equivalent to PCI Express. Say 'y' to enable support for the configuration and management of devices supporting these protocols. Symbol: CXL_BUS [=n] Type : tristate Defined at drivers/cxl/Kconfig:2 Prompt: CXL (Compute Express Link) Devices Support Depends on: PCI [=y] Location: -> Device Drivers -> PCI support (PCI [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>

3 years

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel April 2021