kernel February 2021

kernel@lists.fedoraproject.org

24 participants
153 discussions

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

← Newer
1
...
6
7
8
9
10
11
12
...
16
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel February 2021