Home
last modified time | relevance | path

Searched full:markings (Results 1 – 23 of 23) sorted by relevance

/linux/net/netfilter/
H A Dxt_CONNSECMARK.c3 * This module is used to copy security markings from packets
4 * to connections, and restore security markings from connections
H A DKconfig128 This option enables security markings to be applied to
868 The CONNSECMARK target copies security markings from packets
869 to connections, and restores security markings from connections
/linux/arch/arm/boot/dts/vt8500/
H A Dwm8950.dtsi6 /* No differences have been discovered vs. WM8850, but chip markings differ */
/linux/Documentation/core-api/
H A Dasm-annotations.rst110 most frequent markings**. They are used for functions with standard calling
115 ``SYM_FUNC_START_WEAK`` and ``SYM_FUNC_START_WEAK_NOALIGN`` markings are
/linux/arch/arm/kernel/
H A Delf.c98 * *this column has no architectural effect: NX markings are ignored by
/linux/Documentation/devicetree/bindings/iio/adc/
H A Dmicrochip,mcp3564.yaml86 The device address is part of the device markings to avoid
/linux/net/ipv4/
H A Dtcp_rate.c54 * heuristics. We don't want spurious RTOs or loss markings to cause in tcp_rate_skb_sent()
/linux/security/
H A Dcommoncap.c320 * affects the security markings on that inode, and if it is, should
336 * cap_inode_killpriv - Erase the security markings on an inode
341 * Erase the privilege-enhancing security markings on an inode.
/linux/arch/x86/include/asm/
H A Delf.h280 * *this column has no architectural effect: NX markings are ignored by
/linux/samples/bpf/
H A Dhbm.c372 // ECN CE markings in run_bpf_prog()
/linux/Documentation/security/
H A Dcredentials.rst227 File Markings
/linux/arch/arm64/boot/dts/rockchip/
H A Drk3326-gameforce-chi.dts767 * is an 8-pin SOIC with no markings located right next to the left ADC
/linux/include/linux/
H A Dpage-flags.h583 * Private page markings that may be used by the filesystem that owns the page in PAGEFLAG()
H A Drcupdate.h497 * multiple pointers markings to match different RCU implementations
H A Diommu.h26 * markings, and certain devices are capable of issuing transactions marked as
/linux/drivers/iio/adc/
H A Dmcp3564.c1120 * The device address is part of the device markings to avoid in mcp3564_config()
/linux/kernel/bpf/
H A Dverifier.c2304 /* The register can already have a range from prior markings. in reg_is_init_pkt_pointer()
4289 * No further markings in parent are necessary in backtrack_insn()
4598 * because precision markings in current non-checkpointed state are in mark_all_scalars_precise()
4678 * In the former case, precise markings in current state are completely
4680 * checkpointed ("old") state precise markings are important, and if old
4684 * markings and any required parent states' precise markings are enforced
4688 * actually matters is any of the precise markings propagated into current
4691 * markings set or not.
4700 * what we mentioned above about state comparison ignoring precise markings
4702 * markings *at will* during instruction verification process. But as verifier
[all …]
/linux/drivers/dma/
H A Dste_dma40.c84 /* Bit markings for allocation map */
/linux/Documentation/
H A Dmemory-barriers.txt1814 volatile markings, the compiler would be well within its rights to
/linux/Documentation/translations/sp_SP/
H A Dmemory-barriers.txt1886 hay markings volátiles, el compilador estaría en su derecho de
/linux/drivers/bluetooth/
H A Dbtusb.c2560 * - 0x7558: IC markings FR3191AHAL 749H15143 (HCI rev/sub-version: 0x0709) in btusb_setup_csr()
/linux/drivers/scsi/
H A Dscsi_debug.c7116 ramp[510] = 0x55; /* magic partition markings */ in sdebug_build_parts()
/linux/scripts/
H A Dcheckpatch.pl4230 # check for old HOTPLUG __dev<foo> section markings