FreeBSD Bugzilla – Attachment 160227 Details for
Bug 112556
[patch]: sysctl(8) needs to fix multi-lineal descriptions
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
[patch]
Fix the strings in sys/dev/pci.c
sys.dev.pci.pci.c.patch (text/plain), 2.72 KB, created by
Willem Jan Withagen
on 2015-08-22 22:20:24 UTC
(
hide
)
Description:
Fix the strings in sys/dev/pci.c
Filename:
MIME Type:
Creator:
Willem Jan Withagen
Created:
2015-08-22 22:20:24 UTC
Size:
2.72 KB
patch
obsolete
>Index: sys/dev/pci/pci.c >=================================================================== >--- sys/dev/pci/pci.c (revision 287027) >+++ sys/dev/pci/pci.c (working copy) >@@ -306,24 +306,25 @@ > TUNABLE_INT("hw.pci.enable_io_modes", &pci_enable_io_modes); > SYSCTL_INT(_hw_pci, OID_AUTO, enable_io_modes, CTLFLAG_RW, > &pci_enable_io_modes, 1, >- "Enable I/O and memory bits in the config register. Some BIOSes do not\n\ >-enable these bits correctly. We'd like to do this all the time, but there\n\ >-are some peripherals that this causes problems with."); >+ "Enable I/O and memory bits in the config register. Some BIOSes do not" >+ " enable these bits correctly. We'd like to do this all the time, but" >+ " there\n\ are some peripherals that this causes problems with."); > > static int pci_do_realloc_bars = 0; > TUNABLE_INT("hw.pci.realloc_bars", &pci_do_realloc_bars); > SYSCTL_INT(_hw_pci, OID_AUTO, realloc_bars, CTLFLAG_RW, > &pci_do_realloc_bars, 0, >- "Attempt to allocate a new range for any BARs whose original firmware-assigned ranges fail to allocate during the initial device scan."); >- >+ "Attempt to allocate a new range for any BARs whose original" >+ " firmware-assigned ranges fail to allocate during the initial device" >+ " scan."); > static int pci_do_power_nodriver = 0; > TUNABLE_INT("hw.pci.do_power_nodriver", &pci_do_power_nodriver); > SYSCTL_INT(_hw_pci, OID_AUTO, do_power_nodriver, CTLFLAG_RW, > &pci_do_power_nodriver, 0, >- "Place a function into D3 state when no driver attaches to it. 0 means\n\ >-disable. 1 means conservatively place devices into D3 state. 2 means\n\ >-agressively place devices into D3 state. 3 means put absolutely everything\n\ >-in D3 state."); >+ "Place a function into D3 state when no driver attaches to it. 0 means" >+ " disable. 1 means conservatively place devices into D3 state. 2 means" >+ " agressively place devices into D3 state. 3 means put absolutely" >+ " everything in D3 state."); > > int pci_do_power_resume = 1; > TUNABLE_INT("hw.pci.do_power_resume", &pci_do_power_resume); >@@ -359,9 +360,10 @@ > #endif > TUNABLE_INT("hw.pci.usb_early_takeover", &pci_usb_takeover); > SYSCTL_INT(_hw_pci, OID_AUTO, usb_early_takeover, CTLFLAG_RDTUN, >- &pci_usb_takeover, 1, "Enable early takeover of USB controllers.\n\ >-Disable this if you depend on BIOS emulation of USB devices, that is\n\ >-you use USB devices (like keyboard or mouse) but do not load USB drivers"); >+ &pci_usb_takeover, 1, >+ "Enable early takeover of USB controllers. Disable this if you depend on" >+ " BIOS emulation of USB devices, that is you use USB devices (like" >+ " keyboard or mouse) but do not load USB drivers"); > > static int pci_clear_bars; > TUNABLE_INT("hw.pci.clear_bars", &pci_clear_bars); >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 112556
:
78247
|
160227
|
160742