From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 018/114] drivers: ntb: Kconfig: pedantic formatting
Date: Mon, 11 Mar 2019 14:17:30 +0100 [thread overview]
Message-ID: <1552310346-7629-19-git-send-email-info@metux.net> (raw)
In-Reply-To: <1552310346-7629-1-git-send-email-info@metux.net>
Formatting of Kconfig files doesn't look so pretty, so let the
Great White Handkerchief come around and clean it up.
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
---
drivers/ntb/Kconfig | 20 ++++++++++----------
drivers/ntb/hw/amd/Kconfig | 4 ++--
drivers/ntb/hw/idt/Kconfig | 41 ++++++++++++++++++++---------------------
drivers/ntb/hw/intel/Kconfig | 4 ++--
drivers/ntb/hw/mscc/Kconfig | 8 ++++----
drivers/ntb/test/Kconfig | 26 +++++++++++++-------------
6 files changed, 51 insertions(+), 52 deletions(-)
diff --git a/drivers/ntb/Kconfig b/drivers/ntb/Kconfig
index 95944e5..5ce3fdd 100644
--- a/drivers/ntb/Kconfig
+++ b/drivers/ntb/Kconfig
@@ -2,13 +2,13 @@ menuconfig NTB
tristate "Non-Transparent Bridge support"
depends on PCI
help
- The PCI-E Non-transparent bridge hardware is a point-to-point PCI-E bus
- connecting 2 systems. When configured, writes to the device's PCI
- mapped memory will be mirrored to a buffer on the remote system. The
- ntb Linux driver uses this point-to-point communication as a method to
- transfer data from one system to the other.
+ The PCI-E Non-transparent bridge hardware is a point-to-point PCI-E bus
+ connecting 2 systems. When configured, writes to the device's PCI
+ mapped memory will be mirrored to a buffer on the remote system. The
+ ntb Linux driver uses this point-to-point communication as a method to
+ transfer data from one system to the other.
- If unsure, say N.
+ If unsure, say N.
if NTB
@@ -19,10 +19,10 @@ source "drivers/ntb/test/Kconfig"
config NTB_TRANSPORT
tristate "NTB Transport Client"
help
- This is a transport driver that enables connected systems to exchange
- messages over the ntb hardware. The transport exposes a queue pair api
- to client drivers.
+ This is a transport driver that enables connected systems to exchange
+ messages over the ntb hardware. The transport exposes a queue pair api
+ to client drivers.
- If unsure, say N.
+ If unsure, say N.
endif # NTB
diff --git a/drivers/ntb/hw/amd/Kconfig b/drivers/ntb/hw/amd/Kconfig
index cfe903c..9a90f17 100644
--- a/drivers/ntb/hw/amd/Kconfig
+++ b/drivers/ntb/hw/amd/Kconfig
@@ -2,6 +2,6 @@ config NTB_AMD
tristate "AMD Non-Transparent Bridge support"
depends on X86_64
help
- This driver supports AMD NTB on capable Zeppelin hardware.
+ This driver supports AMD NTB on capable Zeppelin hardware.
- If unsure, say N.
+ If unsure, say N.
diff --git a/drivers/ntb/hw/idt/Kconfig b/drivers/ntb/hw/idt/Kconfig
index f8948cf..5d106ac 100644
--- a/drivers/ntb/hw/idt/Kconfig
+++ b/drivers/ntb/hw/idt/Kconfig
@@ -3,28 +3,27 @@ config NTB_IDT
depends on PCI
select HWMON
help
- This driver supports NTB of cappable IDT PCIe-switches.
+ This driver supports NTB of cappable IDT PCIe-switches.
- Some of the pre-initializations must be made before IDT PCIe-switch
- exposes it NT-functions correctly. It should be done by either proper
- initialisation of EEPROM connected to master smbus of the switch or
- by BIOS using slave-SMBus interface changing corresponding registers
- value. Evidently it must be done before PCI bus enumeration is
- finished in Linux kernel.
+ Some of the pre-initializations must be made before IDT PCIe-switch
+ exposes it NT-functions correctly. It should be done by either proper
+ initialisation of EEPROM connected to master smbus of the switch or
+ by BIOS using slave-SMBus interface changing corresponding registers
+ value. Evidently it must be done before PCI bus enumeration is
+ finished in Linux kernel.
- First of all partitions must be activated and properly assigned to all
- the ports with NT-functions intended to be activated (see SWPARTxCTL
- and SWPORTxCTL registers). Then all NT-function BARs must be enabled
- with chosen valid aperture. For memory windows related BARs the
- aperture settings shall determine the maximum size of memory windows
- accepted by a BAR. Note that BAR0 must map PCI configuration space
- registers.
+ First of all partitions must be activated and properly assigned to all
+ the ports with NT-functions intended to be activated (see SWPARTxCTL
+ and SWPORTxCTL registers). Then all NT-function BARs must be enabled
+ with chosen valid aperture. For memory windows related BARs the
+ aperture settings shall determine the maximum size of memory windows
+ accepted by a BAR. Note that BAR0 must map PCI configuration space
+ registers.
- It's worth to note, that since a part of this driver relies on the
- BAR settings of peer NT-functions, the BAR setups can't be done over
- kernel PCI fixups. That's why the alternative pre-initialization
- techniques like BIOS using SMBus interface or EEPROM should be
- utilized.
-
- If unsure, say N.
+ It's worth to note, that since a part of this driver relies on the
+ BAR settings of peer NT-functions, the BAR setups can't be done over
+ kernel PCI fixups. That's why the alternative pre-initialization
+ techniques like BIOS using SMBus interface or EEPROM should be
+ utilized.
+ If unsure, say N.
diff --git a/drivers/ntb/hw/intel/Kconfig b/drivers/ntb/hw/intel/Kconfig
index 91f995e..c166d50 100644
--- a/drivers/ntb/hw/intel/Kconfig
+++ b/drivers/ntb/hw/intel/Kconfig
@@ -2,6 +2,6 @@ config NTB_INTEL
tristate "Intel Non-Transparent Bridge support"
depends on X86_64
help
- This driver supports Intel NTB on capable Xeon and Atom hardware.
+ This driver supports Intel NTB on capable Xeon and Atom hardware.
- If unsure, say N.
+ If unsure, say N.
diff --git a/drivers/ntb/hw/mscc/Kconfig b/drivers/ntb/hw/mscc/Kconfig
index 013ed67..74ec015 100644
--- a/drivers/ntb/hw/mscc/Kconfig
+++ b/drivers/ntb/hw/mscc/Kconfig
@@ -2,8 +2,8 @@ config NTB_SWITCHTEC
tristate "MicroSemi Switchtec Non-Transparent Bridge Support"
select PCI_SW_SWITCHTEC
help
- Enables NTB support for Switchtec PCI switches. This also
- selects the Switchtec management driver as they share the same
- hardware interface.
+ Enables NTB support for Switchtec PCI switches. This also
+ selects the Switchtec management driver as they share the same
+ hardware interface.
- If unsure, say N.
+ If unsure, say N.
diff --git a/drivers/ntb/test/Kconfig b/drivers/ntb/test/Kconfig
index a5d0eda..416ab56 100644
--- a/drivers/ntb/test/Kconfig
+++ b/drivers/ntb/test/Kconfig
@@ -1,27 +1,27 @@
config NTB_PINGPONG
tristate "NTB Ping Pong Test Client"
help
- This is a simple ping pong driver that exercises the scratchpads and
- doorbells of the ntb hardware. This driver may be used to test that
- your ntb hardware and drivers are functioning at a basic level.
+ This is a simple ping pong driver that exercises the scratchpads and
+ doorbells of the ntb hardware. This driver may be used to test that
+ your ntb hardware and drivers are functioning at a basic level.
- If unsure, say N.
+ If unsure, say N.
config NTB_TOOL
tristate "NTB Debugging Tool Test Client"
help
- This is a simple debugging driver that enables the doorbell and
- scratchpad registers to be read and written from the debugfs. This
- enables more complicated debugging to be scripted from user space.
- This driver may be used to test that your ntb hardware and drivers are
- functioning at a basic level.
+ This is a simple debugging driver that enables the doorbell and
+ scratchpad registers to be read and written from the debugfs. This
+ enables more complicated debugging to be scripted from user space.
+ This driver may be used to test that your ntb hardware and drivers are
+ functioning at a basic level.
- If unsure, say N.
+ If unsure, say N.
config NTB_PERF
tristate "NTB RAW Perf Measuring Tool"
help
- This is a tool to measure raw NTB performance by transferring data
- to and from the window without additional software interaction.
+ This is a tool to measure raw NTB performance by transferring data
+ to and from the window without additional software interaction.
- If unsure, say N.
+ If unsure, say N.
--
1.9.1
next prev parent reply other threads:[~2019-03-11 13:30 UTC|newest]
Thread overview: 123+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 13:17 Kconfig: Great White Handkerchief going round Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 001/114] drivers: gpio: Kconfig: pedantic formatting Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 002/114] drivers: iio: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 003/114] drivers: input: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 004/114] drivers: watchdog: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 005/114] fs: 9p: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 006/114] drivers: uio: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 007/114] drivers: leds: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 008/114] drivers: ata: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 009/114] drivers: ide: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 010/114] sound: soc: qcom: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 011/114] drivers: mmc: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 012/114] arch: um: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 013/114] arch: um: drivers: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 014/114] drivers: fpga: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 015/114] drivers: nvme: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 016/114] drivers: pcmcia: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 017/114] drivers: infiniband: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` Enrico Weigelt, metux IT consult [this message]
2019-03-11 13:17 ` [PATCH 019/114] drivers: uwb: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 020/114] drivers: thermal: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 021/114] drivers: scsi: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 022/114] security: keys: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 023/114] drivers: video: fbdev: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 024/114] s390: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 025/114] arch: sh: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 026/114] arch: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 027/114] virt: kvm: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 028/114] arch: alpha: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 029/114] sound: drivers: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 030/114] sound: oao: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 031/114] secuirty: integrity: ima: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 032/114] sound: Kconfig: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 033/114] mm: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 034/114] arch: arm: " Enrico Weigelt, metux IT consult
2019-03-21 1:55 ` Masahiro Yamada
2019-03-22 16:01 ` Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 035/114] arch: arc: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 036/114] arch: amd64: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 037/114] arch: powerpc: " Enrico Weigelt, metux IT consult
2019-04-29 3:45 ` Michael Ellerman
2019-03-11 13:17 ` [PATCH 038/114] arch: mips: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 039/114] drivers: video: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 040/114] drivers: usb: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 041/114] drivers: w1: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 042/114] drivers: tty: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 043/114] drivers: staging: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 044/114] kernel: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 045/114] drivers: char: tpm: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 046/114] lib: " Enrico Weigelt, metux IT consult
2019-03-11 13:17 ` [PATCH 047/114] net: caif: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 048/114] samples: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 049/114] security: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 050/114] net: " Enrico Weigelt, metux IT consult
2019-03-21 2:10 ` Masahiro Yamada
2019-03-11 13:18 ` [PATCH 051/114] fs: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 052/114] arch: x86: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 053/114] drivers: pinctrl: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 054/114] drivers: platform: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 055/114] drivers: crypto: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 056/114] drivers: spi: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 057/114] drivers: power: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 058/114] drivers: net: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 059/114] drivers: phy: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 060/114] drivers: pci: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 061/114] drivers: sbus: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 062/114] init: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 063/114] drivers: media: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 064/114] drivers: parisc: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 065/114] drivers: regulator: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 066/114] drivers: mtd: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 067/114] drivers: i2c: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 068/114] drivers: mfd: " Enrico Weigelt, metux IT consult
2019-04-02 4:10 ` Lee Jones
2019-03-11 13:18 ` [PATCH 069/114] drivers: perf: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 070/114] drivers: hwtracing: coresight: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 071/114] drivers: isdn: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 072/114] drivers: macintosh: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 073/114] drivers: gpu: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 074/114] drivers: md: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 075/114] drivers: soc: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 076/114] drivers: virt: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 077/114] drivers: clk: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 078/114] drivers: firmware: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 079/114] drivers: char: " Enrico Weigelt, metux IT consult
2019-03-11 14:08 ` Corey Minyard
2019-03-21 1:58 ` Masahiro Yamada
2019-03-11 13:18 ` [PATCH 080/114] drivers: devfreq: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 081/114] drivers: memstick: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 082/114] drivers: pwm: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 083/114] drivers: vme: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 084/114] drivers: acpi: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 085/114] drivers: auxdisplay: " Enrico Weigelt, metux IT consult
2019-03-12 15:24 ` Miguel Ojeda
2019-03-11 13:18 ` [PATCH 086/114] drivers: cpufreq: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 087/114] drivers: hwmon: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 088/114] drivers: irqchip: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 089/114] drivers: virtio: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 090/114] certs: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 091/114] block: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 092/114] drivers: dma: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 093/114] arch: h8300: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 094/114] arch: nds32: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 095/114] arch: ia64: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 096/114] arch: openrisc: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 097/114] arch: riscv: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 098/114] crypto: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 099/114] drivers: block: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 100/114] arch: sparc: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 101/114] drivers: atm: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 102/114] drivers: cpuidle: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 103/114] drivers: iommu: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 104/114] drivers: edac: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 105/114] drivers: hid: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 106/114] drivers: rtc: " Enrico Weigelt, metux IT consult
2019-03-11 13:18 ` [PATCH 107/114] drivers: xen: " Enrico Weigelt, metux IT consult
2019-03-11 13:19 ` [PATCH 108/114] drivers: firmware_loader: " Enrico Weigelt, metux IT consult
2019-03-11 13:19 ` [PATCH 109/114] drivers: clocksource: " Enrico Weigelt, metux IT consult
2019-03-11 13:19 ` [PATCH 110/114] drivers: hv: " Enrico Weigelt, metux IT consult
2019-03-11 13:19 ` [PATCH 111/114] drivers: mcb: " Enrico Weigelt, metux IT consult
2019-03-11 13:19 ` [PATCH 112/114] drivers: misc: " Enrico Weigelt, metux IT consult
2019-03-11 13:19 ` [PATCH 113/114] drivers: rpmsg: " Enrico Weigelt, metux IT consult
2019-03-11 13:19 ` [PATCH 114/114] arch: arm: boot: dts: " Enrico Weigelt, metux IT consult
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1552310346-7629-19-git-send-email-info@metux.net \
--to=info@metux.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®