Home
last modified time | relevance | path

Searched full:breach (Results 1 – 25 of 25) sorted by relevance

/kernel/linux/linux-5.10/LICENSES/dual/
DCDDL-1.0281 cure such breach within 30 days of becoming aware of the
282 breach. Provisions which, by their nature, must remain in effect
DMPL-1.1336 such breach within 30 days of becoming aware of the breach. All
/kernel/linux/linux-6.6/LICENSES/dual/
DCDDL-1.0281 cure such breach within 30 days of becoming aware of the
282 breach. Provisions which, by their nature, must remain in effect
DMPL-1.1336 such breach within 30 days of becoming aware of the breach. All
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/thermal/
Dnvidia,tegra124-soctherm.txt94 property is missing. When the thermtrips property is present, the breach of a
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/thermal/
Dnvidia,tegra124-soctherm.yaml165 is present, the breach of a critical trip point is reported back to
/kernel/linux/linux-5.10/Documentation/crypto/
Duserspace-if.rst255 Such breach in integrity is marked with the -EBADMSG error code.
/kernel/linux/linux-6.6/Documentation/crypto/
Duserspace-if.rst255 Such breach in integrity is marked with the -EBADMSG error code.
/kernel/linux/linux-5.10/include/crypto/
Daead.h40 * a breach in the integrity of the message. In essence, that -EBADMSG error
/kernel/linux/linux-6.6/include/crypto/
Daead.h39 * a breach in the integrity of the message. In essence, that -EBADMSG error
/kernel/linux/linux-6.6/drivers/thermal/tegra/
Dtegra30-tsensor.c226 * TSENSOR doesn't trigger interrupt on the "low" temperature breach, in tegra_tsensor_set_trips()
Dsoctherm.c1428 seq_printf(s, "THROT STATUS: breach(%d) ", state); in regs_show()
/kernel/linux/linux-5.10/drivers/devfreq/
Dtegra30-devfreq.c90 /* Factors applied to boost_freq every consecutive watermark breach */
/kernel/linux/linux-6.6/kernel/sched/
Dpsi.c464 /* Check for stall activity or a previous threshold breach */ in update_triggers()
503 /* Reset threshold breach flag once event got generated */ in update_triggers()
Dfair.c3715 * at 0-lag point, thus breach assumption. Proof completed. in reweight_eevdf()
/kernel/linux/linux-6.6/drivers/devfreq/
Dtegra30-devfreq.c85 /* Factors applied to boost_freq every consecutive watermark breach */
/kernel/linux/linux-6.6/drivers/media/pci/saa7164/
Dsaa7164-core.c284 printk(KERN_ERR "%s() buf %p guard buffer breach\n", in saa7164_work_enchandler_helper()
/kernel/linux/linux-6.6/drivers/net/wireless/ath/ath6kl/
Dwmi.h1862 * Indicate the RSSI events to host. Events are indicated when we breach a
/kernel/linux/linux-5.10/drivers/net/wireless/ath/ath6kl/
Dwmi.h1862 * Indicate the RSSI events to host. Events are indicated when we breach a
/kernel/linux/linux-5.10/drivers/media/pci/saa7164/
Dsaa7164-core.c284 printk(KERN_ERR "%s() buf %p guard buffer breach\n", in saa7164_work_enchandler_helper()
/kernel/linux/linux-6.6/mm/
Dvmstat.c208 * that even the maximum amount of drift will not accidentally breach in calculate_pressure_threshold()
/kernel/linux/linux-5.10/mm/
Dvmstat.c182 * that even the maximum amount of drift will not accidentally breach in calculate_pressure_threshold()
/kernel/linux/linux-5.10/drivers/thermal/tegra/
Dsoctherm.c1466 seq_printf(s, "THROT STATUS: breach(%d) ", state); in regs_show()
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dcgroup-v2.rst1481 Because breach of the high limit doesn't trigger the OOM killer but
/kernel/linux/linux-6.6/Documentation/admin-guide/
Dcgroup-v2.rst1652 Because breach of the high limit doesn't trigger the OOM killer but