/linux/net/netfilter/ |
H A D | nft_bitwise.c | 288 const struct nft_bitwise *bitwise; in nft_bitwise_reduce() local 296 bitwise = nft_expr_priv(track->regs[priv->dreg].selector); in nft_bitwise_reduce() 299 track->regs[priv->dreg].bitwise && in nft_bitwise_reduce() 300 track->regs[priv->dreg].bitwise->ops == expr->ops && in nft_bitwise_reduce() 301 priv->sreg == bitwise->sreg && in nft_bitwise_reduce() 302 priv->dreg == bitwise->dreg && in nft_bitwise_reduce() 303 priv->op == bitwise->op && in nft_bitwise_reduce() 304 priv->len == bitwise->len && in nft_bitwise_reduce() 305 !memcmp(&priv->mask, &bitwise->mask, sizeof(priv->mask)) && in nft_bitwise_reduce() 306 !memcmp(&priv->xor, &bitwise->xor, sizeof(priv->xor)) && in nft_bitwise_reduce() [all …]
|
H A D | nft_fib.c | 200 if (!track->regs[priv->dreg].bitwise) in nft_fib_reduce()
|
H A D | nft_osf.c | 148 if (!track->regs[priv->dreg].bitwise) in nft_osf_reduce()
|
H A D | nft_xfrm.c | 281 if (!track->regs[priv->dreg].bitwise) in nft_xfrm_reduce()
|
H A D | nft_socket.c | 271 if (!track->regs[priv->dreg].bitwise) in nft_socket_reduce()
|
H A D | nft_hash.c | 217 if (!track->regs[priv->dreg].bitwise) in nft_symhash_reduce()
|
/linux/Documentation/dev-tools/ |
H A D | sparse.rst | 28 which makes PM_SUSPEND and PM_RESUME "bitwise" integers (the "__force" is 29 there because sparse will complain about casting to/from a bitwise type, 50 constant zero as a bitwise integer type without sparse ever complaining. 51 This is because "bitwise" (as the name implies) was designed for making 52 sure that bitwise types don't get mixed up (little-endian vs big-endian
|
/linux/Documentation/translations/zh_CN/dev-tools/ |
H A D | sparse.rst | 40 这样会使 PM_SUSPEND 和 PM_RESUME 成为位方式(bitwise)整数(使用"__force" 61 不用担心 sparse 会抱怨。这是因为"bitwise"(恰如其名)是用来确保不同位方
|
/linux/Documentation/translations/zh_TW/dev-tools/ |
H A D | sparse.rst | 39 這樣會使 PM_SUSPEND 和 PM_RESUME 成爲位方式(bitwise)整數(使用"__force" 60 不用擔心 sparse 會抱怨。這是因爲"bitwise"(恰如其名)是用來確保不同位方
|
/linux/scripts/atomic/kerneldoc/ |
H A D | and | 3 * ${class}${atomicname}() - atomic bitwise AND with ${desc_order} ordering
|
H A D | xor | 3 * ${class}${atomicname}() - atomic bitwise XOR with ${desc_order} ordering
|
H A D | or | 3 * ${class}${atomicname}() - atomic bitwise OR with ${desc_order} ordering
|
H A D | andnot | 3 * ${class}${atomicname}() - atomic bitwise AND NOT with ${desc_order} ordering
|
/linux/include/uapi/linux/ |
H A D | types.h | 28 #define __bitwise __attribute__((bitwise))
|
/linux/tools/include/linux/ |
H A D | types.h | 46 #define __bitwise __attribute__((bitwise))
|
/linux/scripts/dtc/libfdt/ |
H A D | libfdt_env.h | 19 #define FDT_BITWISE __attribute__((bitwise))
|
/linux/Documentation/pcmcia/ |
H A D | driver.rst | 17 a bitwise or-ed combination from PCMCIA_DEV_ID_MATCH_* constants
|
/linux/Documentation/devicetree/bindings/cpufreq/ |
H A D | nvidia,tegra20-cpufreq.txt | 20 A bitwise AND is performed against these values and if any bit
|
/linux/drivers/char/mwave/ |
H A D | README | 7 mwave_debug=value, where value is bitwise OR of trace flags:
|
/linux/lib/xz/ |
H A D | Kconfig | 43 been replaced with a bitwise-negation of the lc/lp/pb
|
/linux/Documentation/watchdog/ |
H A D | pcwd-watchdog.rst | 49 WDIOF_* bitwise-anded into the value. (The comments
|
/linux/Documentation/driver-api/ |
H A D | parport-lowlevel.rst | 154 hardware. It consists of flags which may be bitwise-ored together: 413 ``flags`` may be a bitwise combination of the following flags: 1492 bitwise-or'ed together: 1530 bitwise-or'ed together: 1568 bitwise-or'ed together: 1608 bitwise-or'ed together:
|
/linux/Documentation/bpf/ |
H A D | cpumasks.rst | 273 callers can also perform bitwise operations between multiple cpumasks using 286 bitwise operators (and queried).
|
/linux/Documentation/filesystems/spufs/ |
H A D | spu_create.rst | 38 The parameter flags can be zero or any bitwise or'd combination of the
|
/linux/Documentation/ABI/testing/ |
H A D | sysfs-driver-w1_therm | 171 Bit masks to read/write (bitwise OR):
|