From: Fedora Kernel Team <kernel-team@xxxxxxxxxxxxxxxxx>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_CAN_ISOTP:
CAN Transport Protocols offer support for segmented Point-to-Point
communication between CAN nodes via two defined CAN Identifiers.
As CAN frames can only transport a small amount of data bytes
(max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
segmentation is needed to transport longer PDUs as needed e.g. for
vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN traffic.
This protocol driver implements data transfers according to
ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.
If you want to perform automotive vehicle diagnostic services (UDS),
say 'y'.
Symbol: CAN_ISOTP [=n]
Type : tristate
Defined at net/can/Kconfig:58
Prompt: ISO 15765-2:2016 CAN transport protocol
Depends on: NET [=y] && CAN [=m]
Location:
-> Networking support (NET [=y])
-> CAN bus subsystem support (CAN [=m])
---
Cc: Jiri Benc <jbenc@xxxxxxxxxx>
Cc: Marcelo Leitner <mleitner@xxxxxxxxxx>
Cc: Davide Caratti <dcaratti@xxxxxxxxxx>
Cc: Eric Garver <egarver@xxxxxxxxxx>
Cc: Flavio Leitner <fbl@xxxxxxxxxx>
Cc: Florian Westphal <fwestpha@xxxxxxxxxx>
Cc: Guillaume Nault <gnault@xxxxxxxxxx>
Cc: Hangbin Liu <haliu@xxxxxxxxxx>
Cc: Ivan Vecera <ivecera@xxxxxxxxxx>
Cc: Jarod Wilson <jarod@xxxxxxxxxx>
Cc: Lorenzo Bianconi <lorenzo.bianconi@xxxxxxxxxx>
Cc: Paolo Abeni <pabeni@xxxxxxxxxx>
Cc: Phil Sutter <psutter@xxxxxxxxxx>
Cc: Sabrina Dubroca <sdubroca@xxxxxxxxxx>
Cc: Stefano Brivio <sbrivio@xxxxxxxxxx>
Cc: Xin Long <lxin@xxxxxxxxxx>
Signed-off-by: Fedora Kernel Team <kernel-team@xxxxxxxxxxxxxxxxx>
---
.../configs/common/generic/CONFIG_CAN_ISOTP | 1 +
.../pending-common/generic/CONFIG_CAN_ISOTP | 25 -------------------
2 files changed, 1 insertion(+), 25 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_CAN_ISOTP
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CAN_ISOTP
diff --git a/redhat/configs/common/generic/CONFIG_CAN_ISOTP b/redhat/configs/common/generic/CONFIG_CAN_ISOTP
new file mode 100644
index 000000000000..2ebf8768a868
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_CAN_ISOTP
@@ -0,0 +1 @@
+# CONFIG_CAN_ISOTP is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_CAN_ISOTP b/redhat/configs/pending-common/generic/CONFIG_CAN_ISOTP
deleted file mode 100644
index 58dd572e7fc7..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_CAN_ISOTP
+++ /dev/null
@@ -1,25 +0,0 @@
-# CONFIG_CAN_ISOTP:
-#
-# CAN Transport Protocols offer support for segmented Point-to-Point
-# communication between CAN nodes via two defined CAN Identifiers.
-# As CAN frames can only transport a small amount of data bytes
-# (max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
-# segmentation is needed to transport longer PDUs as needed e.g. for
-# vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN traffic.
-# This protocol driver implements data transfers according to
-# ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.
-# If you want to perform automotive vehicle diagnostic services (UDS),
-# say 'y'.
-#
-# Symbol: CAN_ISOTP [=n]
-# Type : tristate
-# Defined at net/can/Kconfig:58
-# Prompt: ISO 15765-2:2016 CAN transport protocol
-# Depends on: NET [=y] && CAN [=m]
-# Location:
-# -> Networking support (NET [=y])
-# -> CAN bus subsystem support (CAN [=m])
-#
-#
-#
-# CONFIG_CAN_ISOTP is not set
--
GitLab
_______________________________________________
kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx
