[OS-BUILD PATCHv3 0/0] [redhat] New configs in drivers/virtio
by Jeremy Cline (via Email Bridge)
From: Jeremy Cline on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/454
NOTE: Truncated patchset since committer email 'ptalbert(a)redhat.com'
does not match the submitter's GitLab public email address
'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_VIRTIO_MEM:
This driver provides access to virtio-mem paravirtualized memory
devices, allowing to hotplug and hotunplug memory.
This driver was only tested under x86-64, but should theoretically
work on all architectures that support memory hotplug and hotremove.
If unsure, say M.
Symbol: VIRTIO_MEM [=m]
Type : tristate
Defined at drivers/virtio/Kconfig:81
Prompt: Virtio mem driver
Depends on: VIRTIO_MENU [=y] && X86_64 [=y] && VIRTIO [=y] &&
MEMORY_HOTPLUG_SPARSE [=y] && MEMORY_HOTREMOVE [=y]
Location:
-> Device Drivers
-> Virtio drivers (VIRTIO_MENU [=y])
Selects: CONTIG_ALLOC [=y]
---
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>
3 years
[OS-BUILD PATCH] [redhat] New configs in drivers/gpu
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_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
3 years
[OS-BUILD PATCH] [redhat] New configs in drivers/vdpa
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.
---
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
3 years
[OS-BUILD PATCHv2 0/0] [redhat] New configs in drivers/vdpa
by Justin Forbes (via Email Bridge)
From: Justin Forbes on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/321
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_VDPA:
Enable this module to support vDPA device that uses a
datapath which complies with virtio specifications with
vendor specific control path.
Symbol: VDPA [=n]
Type : tristate
Defined at drivers/vdpa/Kconfig:2
Prompt: vDPA drivers
Location:
-> Device Drivers
---
Cc: "Michael S. Tsirkin" <mst(a)redhat.com>
Cc: Jason Wang <jasowang(a)redhat.com>
Cc: rhvirt-patches(a)redhat.com
3 years
[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_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 years
[OS-BUILD PATCH] [redhat] New configs in drivers/power
by CKI Gitlab (via Email Bridge)
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 years
[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
[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
[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
[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