Searched full:concerns (Results 1 – 25 of 53) sorted by relevance
123
18 * A large portion of cpqphp_ctrl.c and cpqphp_pci.c concerns resource47 * A large portion of ibmphp_res.c and ibmphp_pci.c concerns resource
9 long overdue, and the current version addresses the following concerns:
43 because of power saving concerns. `fdinfo` users and benchmark applications which
22 Notice: this binding concerns DSI panels connected directly to a master
105 /* The following only concerns PCIe cards. */ in g84_pci_init()
140 * concerns about the more verbose version.
131 based on overhead, complexity and performance concerns.
83 Without the option META_BG, for safety concerns, all block group
132 Intel TXT also helps solve real end user concerns about having
198 * rseq primitive allows us to implement pop without concerns over
417 Q: What are the security concerns involving hvcs?419 A: There are three main security concerns:
311 One example that illustrates some concerns with write operations is
162 address new problems or concerns.
341 differ in detail to address new problems or concerns. See
377 differ in detail to address new problems or concerns. See
283 case 0x002a: /* Error event concerns FMB */ in __zpci_event_error()
317 /* Because of SMP concerns and speed we play a trick.
74 Even if performance and scalability concerns prevent your code from
22 * | 0x4845 B384 [28:27] = 0x2) mode. Common concerns include: high
378 * set to zero and are reserved for future use and compatibility concerns.
259 address new problems or concerns.
421 detail to address new problems or concerns.
240 address new problems or concerns.
427 concerns. See
541 * (currently, afaik, this concerns only the FVT partition