Searched full:don (Results 1 – 25 of 616) sorted by relevance
12345678910>>...25
| /Documentation/PCI/endpoint/function/binding/ |
| D | pci-ntb.rst | 14 revid don't care
15 progif_code don't care
18 cache_line_size don't care
19 subsys_vendor_id don't care
20 subsys_id don't care
21 interrupt_pin don't care
22 msi_interrupts don't care
23 msix_interrupts don't care
|
| D | pci-test.rst | 14 revid don't care
15 progif_code don't care
16 subclass_code don't care
18 cache_line_size don't care
19 subsys_vendor_id don't care
20 subsys_id don't care
|
| /Documentation/arch/x86/x86_64/ |
| D | boot-options.rst | 25 Don't make logs for corrected errors. All events reported
55 Don't overwrite the bios-set CMCI threshold. This boot option
76 Don't use the IO-APIC.
79 Don't use the local APIC
82 Don't use the local APIC (alias for i386 compatibility)
88 Don't set up the APIC timer
91 Don't check the IO-APIC timer. This can work around
105 Don't use the HPET timer.
111 Don't do power saving in the idle loop using HLT, but poll for rescheduling
126 Don't set the cold reboot flag
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | ABI.rst | 14 don't result in breakage. For instance, if a new property is added,
23 1) Maintainers, don't let perfect be the enemy of good. Don't hold up a
30 the old binding. ie. add additional properties, but don't change the
34 4) Don't submit bindings for staging or unstable. That will be decided by
|
| D | writing-bindings.rst | 4 DOs and DON'Ts for designing and writing Devicetree bindings
21 - DON'T refer to Linux or "device driver" in bindings. Bindings should be
30 - DON'T create nodes just for the sake of instantiating drivers. Multi-function
34 - DON'T use 'syscon' alone without a specific compatible string. A 'syscon'
42 - DO make 'compatible' properties specific. DON'T use wildcards in compatible
51 - DON'T redefine common properties. Just reference the definition and define
93 platforms don't need all devices to have 64-bit address and size.
|
| D | .gitignore | 7 # We don't want to ignore the following even if they are dot-files
|
| /Documentation/admin-guide/namespaces/ |
| D | resource-control.rst | 5 There are a lot of kinds of objects in the kernel that don't have
8 enabled in a kernel for people who don't trust their users or their
14 memory user's they don't trust to play nice can use.
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-hid-prodikeys | 4 Contact: Don Prince <dhprince.devel@yahoo.co.uk>
13 Contact: Don Prince <dhprince.devel@yahoo.co.uk>
23 Contact: Don Prince <dhprince.devel@yahoo.co.uk>
|
| /Documentation/staging/ |
| D | xz.rst | 60 CRC32, make sure that you don't use some other integrity check type
79 so don't hesitate to use custom settings. Example::
99 decompression code. I don't know if it could have any use in the
108 matter in practice all, since they don't cause security issues. But
120 Freenode and talk to Larhzu. I don't actively read LKML or other
124 Don't bother Igor Pavlov with questions about the XZ implementation
|
| /Documentation/networking/ |
| D | tc-actions-env-rules.rst | 20 3) Dropping packets you don't own is a no-no. You simply return
27 returned, then all is great and you don't need to do anything.
|
| D | arcnet.rst | 23 you test this and get it working. Or if you don't. Or anything.
36 If you don't e-mail me about your success/failure soon, I may be forced to
37 start SINGING. And we don't want that, do we?
105 versions are available on my WWW page, or via e-mail if you don't have WWW
161 default which is still set in DIP switches on the card. If you don't have the
162 COM20020 data sheets, and you don't know what the other three options refer
171 If you don't give the IO address on the kernel command line, then the driver
278 don't know why the defaults on the Amiga didn't work; write to me if
411 partly crazy. Here's what *I* did. :) Note that I don't include arc0s in
412 my home network; I don't have any NetBSD or AmiTCP computers, so I only
[all …]
|
| /Documentation/scsi/ |
| D | ChangeLog.ips | 8 4.90.11 - Don't actually RESET unless it's physically required
35 - Don't Issue Internal FFDC Command if there are Active Commands
45 4.70.13 - Don't release HA Lock in ips_next() until SC taken off queue
47 - Don't Send CDB's if we already know the device is not present
|
| D | scsi-changer.rst | 25 changer device this is a "don't care", he *only* shuffles around the
77 I don't have any device lists, neither black-list nor white-list. Thus
92 device [ try "dmesg" if you don't see anything ] and should show up in
140 transfer elements. You likely don't need this as the jukebox
141 should provide this information. But some devices don't ...
|
| /Documentation/hwmon/ |
| D | via686a.rst | 27 don't set the address in the BIOS. Look for a BIOS
30 Don't use this unless the driver complains that the
83 don't seem to make any sense, don't look any further: your chip is simply
|
| D | adm1025.rst | 25 * No temperature offset register, but we don't use it anyway.
26 * No INT mode for pin 16. We don't play with it anyway.
|
| D | pc87360.rst | 36 Also note that for the PC87366, initialization levels 2 and 3 don't enable
75 but this driver implements dynamic clock divider selection, so you don't
100 As mentioned above, you don't have to care about this no more.
104 also for the programmable low limits, so don't be surprised if you try to
161 motherboard manufacturers don't seem to care about National Semiconductor's
|
| /Documentation/filesystems/ |
| D | hpfs.rst | 95 that if somebody (I don't know who?) has set "UID", "GID", "MODE" or "DEV"
105 chgrp symlinks but I don't know what is it good for. chmoding symlink results
110 extended attributes and partly in OS2SYS.INI. I don't want (and don't know how)
119 America where people don't care much about codepages and so multiple codepages
139 this codepage - if you don't try to do what I described above :-)
146 should work. If you have OS/2 server, use only read-only mode. I don't know how
148 list, I don't know how to delete them when file is deleted and how to not
221 If you don't install fixpacks, there are many, many more...
259 1.93 Modified, so that it works with kernels >= 2.1.131, I don't know if it
262 Fixed a possible problem with disks > 64G (but I don't have one, so I can't
[all …]
|
| /Documentation/sound/cards/ |
| D | joystick.rst | 32 option is specified. Some drivers don't need options, and the
66 The following drivers don't support gameport natively, but there are
82 support, so you don't have to load ns558 module. Just load "joydev"
89 ALSA ISA drivers don't have the built-in gameport support.
|
| /Documentation/process/ |
| D | management-style.rst | 27 making it painfully obvious to the questioner that we don't have a clue
49 (Corollary:if the people you manage don't know the details better than
71 things that can't be undone. Don't get ushered into a corner from which
101 admitting up-front that you don't have a friggin' clue, and telling
156 (1) don't call people d*ckheads (at least not in public)
213 direction, just don't push too hard.
254 don't try to make it too obvious unless you really **intend** to irritate
257 Similarly, don't be too polite or subtle about things. Politeness easily
272 a while, and you'll feel cleansed. Just don't crap too close to home.
|
| /Documentation/i2c/ |
| D | ten-bit-addresses.rst | 20 * Not all bus drivers support 10-bit addresses. Some don't because the
22 support for example), some don't because nobody bothered adding the
|
| /Documentation/arch/arm/sa1100/ |
| D | serial_uart.rst | 15 > tty device layer handles this just fine, so you don't have to worry about
50 - don't forget to add 'ttySA0', 'console', or the appropriate tty name
|
| /Documentation/driver-api/usb/ |
| D | dma.rst | 27 don't manage dma mappings for URBs.
55 Most drivers should **NOT** be using these primitives; they don't need
81 behavior. Just don't override it; e.g. with ``NETIF_F_HIGHDMA``.
134 they don't have current users. See the source code. Other than the dmasync
|
| /Documentation/devicetree/bindings/thermal/ |
| D | kirkwood-thermal.txt | 4 don't contain a thermal sensor.
|
| /Documentation/driver-api/ |
| D | i2c.rst | 33 SMBus controllers don't support all the protocol options that an I2C
36 i2c_adapter devices which don't support those I2C operations.
|
| /Documentation/fb/ |
| D | sstfb.rst | 17 not completely working...Don't worry, it's still more than usable
22 BTW, If you have only one monitor , and you don't feel like playing
66 (if you don't have a second monitor, you'll have to plug your monitor
75 if you don't have another fb device, this step is superfluous,
167 - the driver don't detect the 4Mb frame buffer voodoos, it seems that
|
12345678910>>...25