/openbmc/linux/drivers/misc/lkdtm/ |
H A D | heap.c | 93 int *base, *val, saw; in lkdtm_READ_AFTER_FREE() local 123 saw = base[offset]; in lkdtm_READ_AFTER_FREE() 124 if (saw != *val) { in lkdtm_READ_AFTER_FREE() 126 pr_info("Memory correctly poisoned (%x)\n", saw); in lkdtm_READ_AFTER_FREE() 158 int saw, *val; in lkdtm_READ_BUDDY_AFTER_FREE() local 180 saw = base[0]; in lkdtm_READ_BUDDY_AFTER_FREE() 181 if (saw != *val) { in lkdtm_READ_BUDDY_AFTER_FREE() 183 pr_info("Memory correctly poisoned (%x)\n", saw); in lkdtm_READ_BUDDY_AFTER_FREE()
|
/openbmc/qemu/scripts/ |
H A D | get_maintainer.pl | 1964 my %saw; 1965 @parms = grep(!$saw{$_}++, @parms); 1972 my %saw; 1974 @parms = grep(!$saw{$_}++, @parms); 2025 my %saw; 2029 if (!$saw{$address}) { 2035 $saw{$address} = 1;
|
/openbmc/linux/arch/arm64/boot/dts/qcom/ |
H A D | msm8996-xiaomi-common.dtsi | 646 qcom,saw-reg = <&saw3>; 648 qcom,saw-slave; 651 qcom,saw-slave; 654 qcom,saw-slave; 657 qcom,saw-leader;
|
H A D | msm8996-oneplus-common.dtsi | 259 qcom,saw-reg = <&saw3>; 262 qcom,saw-slave; 266 qcom,saw-slave; 270 qcom,saw-leader;
|
H A D | msm8996-sony-xperia-tone.dtsi | 590 qcom,saw-reg = <&saw3>; 593 qcom,saw-slave; 597 qcom,saw-slave; 601 qcom,saw-leader;
|
H A D | msm8939.dtsi | 51 qcom,saw = <&saw0>; 69 qcom,saw = <&saw1>; 82 qcom,saw = <&saw2>; 95 qcom,saw = <&saw3>; 107 qcom,saw = <&saw4>; 126 qcom,saw = <&saw5>; 139 qcom,saw = <&saw6>; 152 qcom,saw = <&saw7>;
|
H A D | apq8096-db820c.dts | 600 qcom,saw-reg = <&saw3>; 604 qcom,saw-slave; 607 qcom,saw-slave; 610 qcom,saw-leader;
|
H A D | msm8916.dtsi | 127 qcom,saw = <&cpu0_saw>; 142 qcom,saw = <&cpu1_saw>; 157 qcom,saw = <&cpu2_saw>; 172 qcom,saw = <&cpu3_saw>;
|
/openbmc/linux/Documentation/devicetree/bindings/regulator/ |
H A D | qcom,spmi-regulator.yaml | 30 qcom,saw-reg: 96 qcom,saw-slave: 100 qcom,saw-leader:
|
/openbmc/openbmc/.github/ISSUE_TEMPLATE/ |
H A D | bug_report.md | 16 **Unexpected behavior you saw**
|
/openbmc/linux/tools/power/cpupower/ |
H A D | TODO | 6 - Somewhere saw the ability to read power consumption of
|
/openbmc/linux/arch/arm/boot/dts/qcom/ |
H A D | qcom-ipq4019.dtsi | 52 qcom,saw = <&saw0>; 66 qcom,saw = <&saw1>; 80 qcom,saw = <&saw2>; 94 qcom,saw = <&saw3>; 106 qcom,saw = <&saw_l2>;
|
H A D | qcom-apq8084.dtsi | 37 qcom,saw = <&saw0>; 48 qcom,saw = <&saw1>; 59 qcom,saw = <&saw2>; 70 qcom,saw = <&saw3>; 78 qcom,saw = <&saw_l2>;
|
H A D | qcom-msm8960.dtsi | 30 qcom,saw = <&saw0>; 40 qcom,saw = <&saw1>;
|
H A D | qcom-msm8974.dtsi | 43 qcom,saw = <&saw0>; 54 qcom,saw = <&saw1>; 65 qcom,saw = <&saw2>; 76 qcom,saw = <&saw3>; 84 qcom,saw = <&saw_l2>;
|
H A D | qcom-apq8064.dtsi | 46 qcom,saw = <&saw0>; 57 qcom,saw = <&saw1>; 68 qcom,saw = <&saw2>; 79 qcom,saw = <&saw3>;
|
/openbmc/u-boot/scripts/ |
H A D | get_maintainer.pl | 2373 my %saw; 2374 @parms = grep(!$saw{$_}++, @parms); 2381 my %saw; 2383 @parms = grep(!$saw{$_}++, @parms); 2434 my %saw; 2438 if (!$saw{$address}) { 2444 $saw{$address} = 1;
|
/openbmc/linux/scripts/ |
H A D | get_maintainer.pl | 2438 my %saw; 2439 @parms = grep(!$saw{$_}++, @parms); 2446 my %saw; 2448 @parms = grep(!$saw{$_}++, @parms); 2499 my %saw; 2503 if (!$saw{$address}) { 2509 $saw{$address} = 1;
|
/openbmc/linux/Documentation/devicetree/bindings/soc/qcom/ |
H A D | qcom,spm.yaml | 58 qcom,saw = <&saw0>;
|
/openbmc/linux/drivers/eisa/ |
H A D | Kconfig | 18 the older ISA bus. The EISA bus saw limited use between 1988 and
|
/openbmc/openbmc/poky/meta/recipes-devtools/rust/ |
H A D | rust-cross-canadian.inc | 43 # in those paths and we hit symbol errors. We saw particular problems with symbol
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-pci-devices-aer_stats | 10 saw any problems).
|
/openbmc/linux/sound/pci/cs46xx/ |
H A D | cs46xx_dsp_scb_types.h | 39 u32 saw; /* Source Address Word */ member
|
/openbmc/linux/Documentation/scheduler/ |
H A D | sched-stats.rst | 11 12 which was in the kernel from 2.6.13-2.6.19 (version 13 never saw a kernel
|
/openbmc/linux/Documentation/RCU/ |
H A D | RTFP.txt | 91 1995 also saw the first publication of DYNIX/ptx's RCU mechanism 102 The year 2000 saw an email exchange that would likely have 104 [RustyRussell2000a,RustyRussell2000b]. Instead, 2001 saw the first 137 Later that year saw a paper describing an RCU implementation 154 2006 saw the first best-paper award for an RCU paper [ThomasEHart2006a], 162 2007 saw the journal version of the award-winning RCU paper from 2006 170 2008 saw a journal paper on real-time RCU [DinakarGuniguntala2008IBMSysJ], 1436 like it, but time he saw an opportunity for this technique,
|