mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-19 19:47:03 +07:00
a7f7f6248d
Since commit 84af7a6194 ("checkpatch: kconfig: prefer 'help' over
'---help---'"), the number of '---help---' has been gradually
decreasing, but there are still more than 2400 instances.
This commit finishes the conversion. While I touched the lines,
I also fixed the indentation.
There are a variety of indentation styles found.
a) 4 spaces + '---help---'
b) 7 spaces + '---help---'
c) 8 spaces + '---help---'
d) 1 space + 1 tab + '---help---'
e) 1 tab + '---help---' (correct indentation)
f) 1 tab + 1 space + '---help---'
g) 1 tab + 2 spaces + '---help---'
In order to convert all of them to 1 tab + 'help', I ran the
following commend:
$ find . -name 'Kconfig*' | xargs sed -i 's/^[[:space:]]*---help---/\thelp/'
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
30 lines
1.1 KiB
Plaintext
30 lines
1.1 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
#
|
|
# IEC 62439-3 High-availability Seamless Redundancy
|
|
#
|
|
|
|
config HSR
|
|
tristate "High-availability Seamless Redundancy (HSR)"
|
|
help
|
|
If you say Y here, then your Linux box will be able to act as a
|
|
DANH ("Doubly attached node implementing HSR"). For this to work,
|
|
your Linux box needs (at least) two physical Ethernet interfaces,
|
|
and it must be connected as a node in a ring network together with
|
|
other HSR capable nodes.
|
|
|
|
All Ethernet frames sent over the hsr device will be sent in both
|
|
directions on the ring (over both slave ports), giving a redundant,
|
|
instant fail-over network. Each HSR node in the ring acts like a
|
|
bridge for HSR frames, but filters frames that have been forwarded
|
|
earlier.
|
|
|
|
This code is a "best effort" to comply with the HSR standard as
|
|
described in IEC 62439-3:2010 (HSRv0) and IEC 62439-3:2012 (HSRv1),
|
|
but no compliancy tests have been made. Use iproute2 to select
|
|
the version you desire.
|
|
|
|
You need to perform any and all necessary tests yourself before
|
|
relying on this code in a safety critical system!
|
|
|
|
If unsure, say N.
|