January 2021 - kernel - Fedora Mailing-Lists

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

by GitLab Bridge on behalf of jmflinuxtx

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

3 years

6
7
0 / 0

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

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_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 years

3
2
0 / 0

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

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_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

3 years

5
6
0 / 0

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

by GitLab Bridge on behalf of jeremycline

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

3 years

5
4
0 / 0

[OS-BUILD PATCH] New configs in arch/powerpc

by GitLab Bridge on behalf of jeremycline

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 years

3
2
0 / 0

[OS-BUILD PATCH] New configs in arch/powerpc

by GitLab Bridge on behalf of jeremycline

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

3 years

4
3
0 / 0

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

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_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

3 years

5
6
0 / 0

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

by GitLab Bridge on behalf of jmflinuxtx

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

3 years

5
4
0 / 0

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

by GitLab Bridge on behalf of jmflinuxtx

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 years

3
2
0 / 0

[OS-BUILD PATCH] [redhat] New configs in init/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_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

3 years

6
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel January 2021