Searched full:knowing (Results 1 – 25 of 138) sorted by relevance
123456
72 Userspace applications interested in knowing the name of85 Userspace applications interested in knowing the details of
8 Knowing the EC GPE one can watch the amount of HW events related to
44 consumed by various applications interested in knowing the Privacy
56 * explicitly defined as additional exit points. Knowing all exit points is
80 * explicitly defined as additional exit points. Knowing all exit points is167 * explicitly defined as additional exit points. Knowing all exit points is
81 * explicitly defined as additional exit points. Knowing all exit points is117 * explicitly defined as additional exit points. Knowing all exit points is
106 * explicitly defined as additional exit points. Knowing all exit points is
103 * explicitly defined as additional exit points. Knowing all exit points is
17 received data. However, there is no specified way of knowing if the sent
103 to generate false positives because KCSAN will have no way of knowing127 to generate false positives because KCSAN will have no way of knowing148 to generate false positives because KCSAN will have no way of knowing165 because KCSAN will have no way of knowing that the resulting data race
54 requires knowing how much contiguous physical memory a system has _at compile
41 Userspace is interested in knowing "this LED can produce arbitrary
44 * knowing about this. On devices where the controller is unused in pwm_lpss_probe_platform()
30 * We are interested at knowing from where the interface in intel_gt_sysfs_get_drvdata()
71 * Used in handle_exception() to save a0, a1 and a2 before knowing if we
18 input and reporting a low/high value, without knowing the last value written
57 * Annotate away the various 'relocation to !ENDBR` complaints; knowing that
23 * related to) the actual interrupt number they use. So knowing the IRQ
10 The following symbol definitions rely on you knowing the translation that
32 firmware knowing how they're used).
95 * number, knowing this would reduce the number of cache entries to be in __flush_dcache_page()
78 * printed backtrace as knowing what instance of input in input_setup_polling()
29 * - Knowing the correlation between dma channels and the
41 Knowing that some modules embed a PHY, the actual link is more like ::
18 knowing what messages were updated in a particular kernel version and why.