Searched full:might (Results 1 – 25 of 573) sorted by relevance
12345678910>>...23
| /Documentation/livepatch/ |
| D | cumulative-patches.rst | 5 There might be dependencies between livepatches. If multiple patches need
10 This might become a maintenance nightmare. Especially when more patches
36 As a result, the livepatch authors might maintain sources only for one
42 actually in use. Also the livepatch might then be seen as a "normal"
83 As a result, it might be dangerous to replace newer cumulative patches by
84 older ones. The old livepatches might not provide the necessary callbacks.
86 This might be seen as a limitation in some scenarios. But it makes life
101 A good practice might be to remove shadow variables in the post-unpatch
|
| D | system-state.rst | 13 The problems might come with shadow variables and callbacks. They might
31 The state of the system might get modified either by several livepatch callbacks
99 It might be the original system state or the state modification
113 - Allocate *state->data* when necessary. The allocation might fail
125 - Clean up its own mess in case of error. It might be done by a custom
154 state. It might mean doing nothing.
166 It might be called also during the transition reverse. Therefore it
|
| D | livepatch.rst | 74 the same way to the rest of the system. In this case, the functions might
77 But there are more complex fixes. For example, a patch might change
79 might exchange meaning of some temporary structures and update
249 might want to access functions or data from the original source file
283 together. Note that patched modules might be loaded later than
284 the patch itself and the relevant functions might be patched
320 Second, the error code might be used to refuse loading the module when
349 Note that functions might be patched multiple times. The ftrace handler
357 functions might be patched two times only during the transition period.
363 All enabled patches might get replaced by a cumulative patch that
[all …]
|
| /Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 21 and after a number of such errors are detected the bus might be reset. Note
38 backtracking and restarting the entire programming sequence might be a
39 solution. Alternatively some implementations might directly issue a bus
58 hard-reset might be the best solution.
62 that the Slave might behave in implementation-defined ways. The bus
|
| /Documentation/ABI/stable/ |
| D | sysfs-hypervisor-xen | 7 Might return "<denied>" in case of special security settings
16 Might return "<denied>" in case of special security settings
25 Might return "<denied>" in case of special security settings
56 Might return "<denied>" in case of special security settings
73 Might return "0" in case of special security settings
105 Might return "<denied>" in case of special security settings
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-set-wideband-receiver.rst | 39 This might be useful of receivers that have otherwise narrow band receiver
40 that prevents them to be used with some remotes. Wide band receiver might
46 Wide band receiver might be implictly enabled if you enable
|
| /Documentation/networking/ |
| D | ipv6.rst | 23 its functionality. This might be used when another module
45 on all interfaces. This might be used when one does not wish
65 This might be used when no IPv6 addresses are desired.
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-dma-buffer | 6 buffers. If this alignment requirement is not met samples might
15 that the alignment requirement in samples sets might change
|
| D | sysfs-memory-page-offline | 15 this might change.
40 this might change.
|
| /Documentation/RCU/ |
| D | rcu_dereference.rst | 106 can now be speculated, such that it might happen before the
182 might provide, especially if you are making use of feedback-based
243 You might be surprised that the outcome (r1 == 143 && r2 == 44) is possible,
244 but you should not be. After all, the updater might have been invoked
310 first pointer might be. This lack of knowledge prevents the compiler
311 from carrying out optimizations that otherwise might destroy the ordering
315 But without rcu_dereference(), the compiler knows more than you might
377 2. If the access might be within an RCU read-side critical section
385 3. If the access might be within an RCU read-side critical section
404 is appropriate. In addition, rcu_dereference_raw() might be
[all …]
|
| D | rcubarrier.rst | 19 such readers might hold a reference to them. RCU updates can therefore be
23 given that readers might well leave absolutely no trace of their
26 element p from a linked list might do the following, while holding an
38 context might then be as follows::
44 IRQ context. The function p_callback() might be defined as follows::
68 One might be tempted to try several back-to-back synchronize_rcu()
70 heavy RCU-callback load, then some of the callbacks might be deferred
187 Is there any other situation where rcu_barrier() might
192 Your module might have additional complications. For example, if your
302 Is there any other situation where rcu_barrier() might
|
| D | NMI-RCU.rst | 60 …Why might the rcu_dereference_sched() be necessary on Alpha, given that the code referenced by the…
108 …Why might the rcu_dereference_sched() be necessary on Alpha, given that the code referenced by the…
110 The caller to set_nmi_callback() might well have
114 just after the new handler was set might see the pointer
|
| /Documentation/power/ |
| D | tricks.rst | 7 If you want to trick swsusp/S3 into working, you might want to try:
19 * use vga text console, shut down X. [If you really want X, you might
|
| /Documentation/process/ |
| D | volatile-considered-harmful.rst | 36 change unexpectedly while the_lock is held. Any other code which might
40 compiler might think it knows what will be in shared_data, but the
61 Another situation where one might be tempted to use volatile is
76 - The above-mentioned accessor functions might use volatile on
92 - Pointers to data structures in coherent memory which might be modified
|
| D | clang-format.rst | 76 While it might be tempting to use this to keep a file always in sync with
78 a maintainer, please note that people might be running different
169 might be different and enabling some of these options may approximate
183 You might want to create another ``.clang-format`` file and use that one
|
| /Documentation/core-api/ |
| D | dma-attributes.rst | 50 buffer from CPU domain to device domain. Some advanced use cases might
61 might be a time consuming operation, especially if the buffers are
85 pages). You might want to specify this if:
88 You might know that the accesses are likely to be sequential or
95 might be the case.
|
| /Documentation/driver-api/media/drivers/ |
| D | bttv-devel.rst | 27 If your card isn't listed there, you might check the source code for
34 example. If your board has one, you might have to load a helper
37 you might want to check the video4linux mailing list archive first...
87 card installed, you might to check out if you can read these registers
91 You might also dig around in the ``*.ini`` files of the Windows applications.
|
| /Documentation/dev-tools/kunit/ |
| D | faq.rst | 38 it might require more work than using KUnit on UML.
53 usually just two or three. For example, someone might write an integration
60 code under test. For example, someone might write an end-to-end test for the
72 parameter. This might show details or error messages hidden by the kunit_tool
88 It also preserves any config changes you might make, so you can
|
| /Documentation/hwmon/ |
| D | sl28cpld.rst | 21 supervisor. In the future there might be other flavours and additional
22 hardware monitoring might be supported.
|
| /Documentation/devicetree/bindings/sound/ |
| D | cs42l42.txt | 31 debounce, the tip sense pin might be noisy on a plug event.
43 With no debounce, the tip sense pin might be noisy on an unplug event.
76 hardware setups, a designer might want to tweak this. This is an array of
|
| /Documentation/sound/designs/ |
| D | powersave.rst | 34 Note that you might hear click noise/pop when changing the power
42 consumption, but might result in longer wake-up time and click noise.
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-atlas7.txt | 7 For example, pinctrl might have properties like the following:
75 For example, pinctrl might have subnodes like the following:
|
| /Documentation/arm64/ |
| D | amu.rst | 73 returned by the register reads might not correctly reflect reality. Most
102 - Security reasons: they might expose information about code executed in
115 - Security reasons: they might expose information about code executed
|
| /Documentation/fb/ |
| D | vesafb.rst | 74 If this does not work, this might be because your BIOS does not support
76 Even if your board does, it might be the BIOS which does not. VESA BIOS
89 another (accelerated) X-Server like XF86_SVGA might or might not work.
107 * VBE 3.0 might work too. I have neither a gfx board with VBE 3.0
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-firmware-acpi | 7 the offline failure might lead to memory corruption and crashes)
|
12345678910>>...23