| /openbmc/witherspoon-pfault-analysis/power-sequencer/ |
| H A D | ucd90160.hpp | 182 * @return bool - if we've already logged a fault against
194 * @param[in] page - the page the error was logged against
209 * @return bool - if we've already logged a fault against
220 * against a specific part
225 * against this part
236 * @param[in] input - the input the error was logged against
255 * already been logged against
261 * already been logged against
|
| /openbmc/phosphor-power/power-sequencer/ |
| H A D | ucd90160.hpp | 182 * @return bool - if we've already logged a fault against
194 * @param[in] page - the page the error was logged against
209 * @return bool - if we've already logged a fault against
220 * against a specific part
225 * against this part
236 * @param[in] input - the input the error was logged against
255 * already been logged against
261 * already been logged against
|
| /openbmc/linux/tools/memory-model/scripts/ |
| H A D | README | 11 the results against the expected results recorded in the
29 Check a single litmus test against its "Result:" expected result.
34 Check the specified list of litmus tests against their "Result:"
55 against the .litmus file's "Result:" comment to judge whether
97 # Checks results against Result tags, runs in minutes:
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/tests/browser/ |
| H A D | README | 13 To run tests against Chrome:
20 To run tests against PhantomJS (headless):
27 To run tests against Firefox, you may need to install the Marionette driver,
40 (Note: The Toaster tests have been checked against Firefox 47 with the
46 To run tests against the Selenium Firefox Docker container:
|
| /openbmc/phosphor-fan-presence/control/json/actions/ |
| H A D | action.hpp | 79 * @param[in] zones - Zones the action runs against
82 * sets the zones the action should run against.
137 * @brief Set the zones the action is run against
139 * @param[in] zones - Zones the action runs against
149 * @brief Add a zone to the list of zones the action is run against if its
178 * @brief Trigger the action to run against all of its zones
180 * This is the function used by triggers to run the actions against all the
181 * zones that were configured for the action to run against.
318 * @param[in] zones - Zones the action runs against
|
| H A D | timer_based_actions.hpp | 69 * actions against the given zones and configured groups.
71 * Where any group does not have a configured value to be compared against,
76 * Where all groups have a configured value to compare against, that will be
77 * compared against all members within each group to start/stop the timer.
112 * Sets the zones on this action and the timer's actions to run against
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | ordering.txt | 12 all of the CPU's prior operations against some or all of its
16 against some or all of the CPU's prior accesses or some or all
68 accesses against all subsequent accesses from the viewpoint of all CPUs.
119 typically instead used to provide ordering against RCU read-side critical
263 end in _release. These operations order their own store against all
287 against "y". On x86, the version using smp_store_release() might compile
307 Note that release ordering is guaranteed only against the
308 memory-store portion of the RMW operation, and not against the
322 operations order their own load against all of the CPU's subsequent
333 improves upon smp_rmb() by ordering against subsequent stores as well
[all …]
|
| /openbmc/phosphor-fan-presence/control/json/triggers/ |
| H A D | signal.hpp | 50 * @param[in] group - Group to subscribe signal against
60 * @param[in] group - Group to subscribe signal against
70 * @param[in] group - Group to subscribe signal against
80 * @param[in] group - Group to subscribe signal against
90 * @param[in] group - Group to subscribe signal against
|
| /openbmc/openbmc/poky/documentation/contributor-guide/ |
| H A D | report-defect.rst | 3 Reporting a Defect Against the Yocto Project and OpenEmbedded
8 against BitBake, OpenEmbedded-Core, against any other Yocto Project component
24 several products and components. For example, for a bug against the
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libxml/libxml-libxml-perl/ |
| H A D | disable-libxml2-check.patch | 22 -print "Checking for ability to link against xml2...";
28 - print "Checking for ability to link against libxml2...";
48 +#print "Checking for ability to link against xml2...";
54 +# print "Checking for ability to link against libxml2...";
|
| /openbmc/linux/security/apparmor/ |
| H A D | match.c | 425 * @dfa: the dfa to match @str against (NOT NULL)
427 * @str: the string of bytes to match against the dfa (NOT NULL)
430 * aa_dfa_match_len will match @str against the dfa and return the state it
469 * @dfa: the dfa to match @str against (NOT NULL)
471 * @str: the null terminated string of bytes to match against the dfa (NOT NULL)
473 * aa_dfa_match will match @str against the dfa and return the state it
554 * @dfa: the dfa to match @str against (NOT NULL)
556 * @str: the null terminated string of bytes to match against the dfa (NOT NULL)
559 * aa_dfa_match will match @str against the dfa and return the state it
611 * @dfa: the dfa to match @str against (NOT NULL)
[all …]
|
| /openbmc/linux/drivers/rapidio/ |
| H A D | rio-driver.c | 19 * @id: the RIO device id structure to match against
20 * @rdev: the RIO device structure to match against
79 * @dev: the RIO device structure to match against
109 * @dev: the RIO device structure to match against
181 * @dev: the standard device structure to match against
182 * @drv: the standard driver structure containing the ids to match against
|
| /openbmc/linux/drivers/staging/iio/Documentation/ |
| H A D | inkernel.txt | 18 matched against the datasheet_name field of the iio_chan_spec.
44 * matching dev or dev_name against consumer_dev and consumer_dev_name
45 * matching consumer_channel against consumer_channel in the map
|
| /openbmc/linux/Documentation/ |
| H A D | atomic_t.txt | 180 Where 'unordered' is against other memory locations. Address dependencies are
183 Fully ordered primitives are ordered against everything prior and everything
194 smp_mb__before_atomic() orders all earlier accesses against the RMW op
196 later accesses against the RMW op and all accesses preceding it. However,
226 a RELEASE because it orders preceding instructions against both the read
227 and write parts of the atomic_dec(), and against all following instructions
260 because it would not order the W part of the RMW against the following
|
| /openbmc/linux/fs/verity/ |
| H A D | Kconfig | 21 against the Merkle tree. The file is also made read-only.
28 against a known good value, e.g. from a digital signature).
33 protection against malicious disks vs. an ahead-of-time hash.
|
| /openbmc/linux/drivers/acpi/acpica/ |
| H A D | nsarguments.c | 27 * against the argument type list for a predefined name.
202 * against the count that is specified in the method/object. in acpi_ns_check_argument_count()
219 * We can only check the incoming argument count against the in acpi_ns_check_argument_count()
252 * count against the ACPI specification. We don't validate against in acpi_ns_check_argument_count()
255 * method was checked against the ACPI spec earlier.) in acpi_ns_check_argument_count()
|
| /openbmc/openbmc/poky/meta/recipes-extended/tcp-wrappers/tcp-wrappers-7.6/ |
| H A D | safe_finger.8 | 3 safe_finger \- finger client wrapper that protects against nasty stuff
10 command protects against nasty stuff from finger servers. Use this
|
| /openbmc/linux/crypto/asymmetric_keys/ |
| H A D | restrict.c | 60 * Check the new certificate against the ones in the trust keyring. If one of
160 * the new certificate against the ones in the trust_keyring.
260 * available, auth_ids[2] is matched against in key_or_keyring_common()
314 * Check the new certificate only against the key or keys passed in the data
341 * Check the new certificate against the key or keys passed in the data
342 * parameter and against the keys already linked to the destination keyring. If
|
| /openbmc/openbmc-build-scripts/jenkins/ |
| H A D | run-build-script-ci | 14 # Check code formatting (by running the UT script against this repo).
23 # Run a simple CI against 'sdbusplus' to ensure the run-unit-test script works.
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | ChangeLog.sym53c8xx_2 | 31 - Check against memory allocation failure for SCRIPTZ and add the
33 - Check against GPIO3 pulled low for HVD controllers (driver did
84 - Mask GPCNTL against 0x1c (was 0xfc) for the reading of the NVRAM.
130 - Prepare a new patch against linux-2.4.13.
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | assoc_array.rst | 40 problem, the iterator should lock against modification. Objects will not
144 Compare the object against an index key and return ``true`` if it matches and
199 The caller should lock exclusively against other modifiers of the array.
219 The caller should lock exclusively against other modifiers of the array.
235 The caller should lock exclusively against other modifiers of the array.
249 The caller should lock exclusively against other modifiers and accessors
277 lock exclusively against other modifiers of the array.
298 this is a problem, then modification should be locked against. The
544 this without locking against a read - so we have to replace that node too.
|
| /openbmc/linux/Documentation/bpf/libbpf/ |
| H A D | libbpf_build.rst | 7 against and must be installed on the system for applications to work.
30 To build both static libbpf.a and shared libbpf.so against a custom libelf
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | LPL-1.02 | 49 …) against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and …
51 …der this section, the Commercial Distributor would have to defend claims against the Contributors …
69 …against a Contributor with respect to a patent applicable to software (including a cross-claim or …
|
| H A D | CPL-1.0 | 121 every other Contributor ("Indemnified Contributor") against any losses, damages
123 actions brought by a third party against the Indemnified Contributor to the
139 Commercial Contributor would have to defend claims against the other
174 If Recipient institutes patent litigation against a Contributor with respect to
178 addition, if Recipient institutes patent litigation against any entity
|
| H A D | IPL-1.0 | 117 against any losses, damages and costs (collectively "Losses") arising
119 party against the Indemnified Contributor to the extent caused by the
137 would have to defend claims against the other Contributors related to
172 If Recipient institutes patent litigation against a Contributor with
177 Recipient institutes patent litigation against any entity (including
|