Searched full:possibilities (Results 1 – 25 of 231) sorted by relevance
12345678910
129 * resolve the two possibilities. */ in dbl_fcmp()156 * resolve the two possibilities. */ in dbl_fcmp()
142 * resolve the two possibilities. */ in dbl_fcmp()169 * resolve the two possibilities. */ in dbl_fcmp()
9 * struct omap_hsmmc_dev_attr.flags possibilities
9 /* some have two possibilities for cpuid string */
26 /* struct clksel_rate.flags possibilities */
23 /* struct clksel_rate.flags possibilities */
12 * struct omap_hsmmc_dev_attr.flags possibilities
37 * 32-bit or 64-bit, so we have to cater for both possibilities. in perf_reg_value()
38 * There are five possibilities for how page->flags get laid out. The first
79 * struct clk.flags possibilities114 * @flags: see "struct clk.flags possibilities" above
142 * @flags: see "struct clk.flags possibilities" above167 * struct clk_hw_omap.flags possibilities
82 * struct clk.flags possibilities117 * @flags: see "struct clk.flags possibilities" above
142 * @flags: see "struct clk.flags possibilities" above165 * struct clk_hw_omap.flags possibilities
39 * There are five possibilities for how page->flags get laid out. The first
132 time ago"? Here are some possibilities:147 There are many other possibilities involving the Linux
36 possibilities of lost update and race condition problems should be
38 possibilities of lost update and race condition problems should be
45 non-privileged mounts. This opens up new possibilities for the use of174 original request and its INTERRUPT request. There are two possibilities:
45 non-privileged mounts. This opens up new possibilities for the use of160 original request and its INTERRUPT request. There are two possibilities:
12 scheduling for ages. This document mainly details the current possibilities
10 * The protocol is very simply, there are two possibilities reading or writing.
11 scheduling for ages. This document mainly details the current possibilities