Searched refs:catch (Results 1 – 25 of 43) sorted by relevance
12
| /linux-3.4.99/arch/parisc/ |
| D | Kconfig.debug | 10 in order to catch accidental (and incorrect) writes to such const
|
| /linux-3.4.99/drivers/gpu/drm/radeon/ |
| D | Kconfig | 29 provided by the user, we want to catch and forbid any illegal use
|
| /linux-3.4.99/drivers/staging/wlags49_h2/ |
| D | TODO | 15 are build in to catch most cases but not all
|
| /linux-3.4.99/drivers/staging/wlags49_h25/ |
| D | TODO | 15 are build in to catch most cases but not all
|
| /linux-3.4.99/arch/x86/ |
| D | Kconfig.debug | 90 in order to catch accidental (and incorrect) writes to such const
91 data. This is recommended so that we can catch kernel bugs sooner.
107 This option helps catch unintended modifications to loadable
|
| /linux-3.4.99/fs/proc/ |
| D | array.c | 237 sigset_t *catch) in collect_sigign_sigcatch() argument
247 sigaddset(catch, i); in collect_sigign_sigcatch()
|
| /linux-3.4.99/Documentation/networking/ |
| D | spider_net.txt | 56 flowing, then the tail pointer can catch up to the hardware pointer.
68 RX traffic is flowing, then the head pointer can catch up to the tail
117 pointer will catch up to the head, notice the not-empty condition,
|
| /linux-3.4.99/arch/openrisc/ |
| D | Kconfig | 146 but will catch most of kernel stack overruns and exit gracefuly.
|
| /linux-3.4.99/Documentation/ |
| D | Intel-IOMMU.txt | 51 We also allocate guard pages with each mapping, so we can attempt to catch
|
| D | gpio.txt | 245 To help catch system configuration errors, two calls are defined.
264 given board. Another is to catch conflicts, identifying errors when
|
| /linux-3.4.99/arch/frv/kernel/ |
| D | entry-table.S | 44 # we have to catch the single-step event in break.S and jump to the fixup
|
| D | break.S | 82 # catch the return from a TLB-miss handler that had single-step disabled
|
| /linux-3.4.99/Documentation/scheduler/ |
| D | sched-domains.txt | 80 which should catch most possible errors (described above). It also prints out
|
| /linux-3.4.99/Documentation/development-process/ |
| D | 4.Coding | 208 of us can reach. What we can hope to do, though, is to catch and fix as
211 array of tools which can catch a wide variety of obscure problems in an
383 The other catch is that a developer who changes an internal API is
|
| D | 5.Posting | 21 that interested developers can catch up with your work at any time.
|
| /linux-3.4.99/Documentation/pps/ |
| D | pps.txt | 178 Sometimes one needs to be able not only to catch PPS signals but to produce
|
| /linux-3.4.99/Documentation/trace/ |
| D | mmiotrace.txt | 60 Load the driver you want to trace and use it. Mmiotrace will only catch MMIO
|
| /linux-3.4.99/lib/ |
| D | Kconfig.debug | 132 the analysis would not catch the illegal reference.
386 allocation as well as poisoning memory on free to catch use of freed
504 Say Y here and build SMP to catch missing spinlock initialization
756 catch mistakes with virt_to_page() and friends.
771 Enable this to catch wrong use of the writers count in struct
|
| /linux-3.4.99/arch/blackfin/ |
| D | Kconfig.debug | 100 Say Y here to catch reads/writes to anywhere in the memory range
|
| /linux-3.4.99/Documentation/frv/ |
| D | features.txt | 73 0x00000000 - 0x00000FFF Null pointer catch page
|
| /linux-3.4.99/Documentation/device-mapper/ |
| D | thin-provisioning.txt | 112 will be triggered which a userspace daemon should catch allowing it to
|
| /linux-3.4.99/drivers/gpio/ |
| D | Kconfig | 48 slower. The diagnostics help catch the type of setup errors
|
| /linux-3.4.99/kernel/trace/ |
| D | Kconfig | 241 Basic tracer to catch the syscall entry and exit events.
|
| /linux-3.4.99/Documentation/m68k/ |
| D | kernel-options.txt | 291 Syntax: dmasound=[<buffers>,<buffer-size>[,<catch-radius>]]
296 buffer in kilobytes (minimum 4, default 32) and <catch-radius> says
|
| /linux-3.4.99/Documentation/serial/ |
| D | computone.txt | 437 X # The test for blank "type" will catch the stats lead-in lines
|
12