| /linux/net/netfilter/ |
| H A D | nf_nat_proto.c | 525 } *inside; in nf_nat_icmp_reply_translation()
534 if (skb_ensure_writable(skb, hdrlen + sizeof(*inside))) in nf_nat_icmp_reply_translation()
539 inside = (void *)skb->data + hdrlen; in nf_nat_icmp_reply_translation()
540 if (inside->icmp.type == ICMP_REDIRECT) { in nf_nat_icmp_reply_translation()
559 if (!nf_nat_ipv4_manip_pkt(skb, hdrlen + sizeof(inside->icmp), in nf_nat_icmp_reply_translation()
564 /* Reloading "inside" here since manip_pkt may reallocate */ in nf_nat_icmp_reply_translation()
565 inside = (void *)skb->data + hdrlen; in nf_nat_icmp_reply_translation()
566 inside->icmp.checksum = 0; in nf_nat_icmp_reply_translation()
567 inside->icmp.checksum = in nf_nat_icmp_reply_translation()
840 } *inside; in nf_nat_icmpv6_reply_translation()
524 } *inside; nf_nat_icmp_reply_translation() local
839 } *inside; nf_nat_icmpv6_reply_translation() local
[all...] |
| /linux/rust/syn/ |
| H A D | verbatim.rs | 22 if let Some((inside, _span, after)) = cursor.group(Delimiter::None) { in between()
24 cursor = inside; in between()
|
| /linux/Documentation/devicetree/bindings/input/ |
| H A D | dlink,dir685-touchkeys.txt | 5 board inside the router is named E119921.
7 The touchkey device node should be placed inside an I2C bus node.
|
| /linux/fs/affs/ |
| H A D | dir.c | 120 goto inside; in affs_readdir()
136 goto inside; in affs_readdir()
144 inside: in affs_readdir()
|
| /linux/Documentation/accel/ |
| H A D | introduction.rst | 11 These devices can be either stand-alone ASICs or IP blocks inside an SoC/GPU.
20 or an IP inside a SoC (e.g. laptop web camera). These devices
24 type of device can be stand-alone or an IP inside a SoC or a GPU. It will
34 a method of scaling-up/out, i.e. connecting to other training cards inside
46 Because this type of devices can be an IP inside GPUs or have similar
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | v4l2-selection-targets.rst | 47 - Bounds of the crop rectangle. All valid crop rectangles fit inside
70 inside the compose bounds rectangle.
|
| H A D | selection-api-configuration.rst | 40 active cropping area must lie completely inside the capture boundaries.
59 bounds rectangle. The composing rectangle must lie completely inside
74 be changed by the hardware. The content of pixels that lie inside the
100 must lie completely inside the crop boundaries and the driver may
111 composing rectangle must lie completely inside the bounds rectangle. The
|
| H A D | ext-ctrls-rf-tuner.rst | 18 inside a metal box, while newer ones are highly integrated chips
77 located inside mixer block, where RF signal is down-converted by the
|
| /linux/Documentation/devicetree/bindings/mmc/ |
| H A D | sdhci-st.txt | 10 subsystem (mmcss) inside the FlashSS (available in STiH407 SoC
27 to configure DLL inside the flashSS, if so reg-names must also be
32 for eMMC on stih407 family silicon to configure DLL inside FlashSS.
|
| /linux/Documentation/arch/arm/ |
| H A D | memory.rst | 43 DTCM mounted inside the CPU.
46 ITCM mounted inside the CPU.
101 must not access any memory which is not mapped inside their 0x0001000
|
| H A D | tcm.rst | 8 This is usually just a few (4-64) KiB of RAM inside the ARM
11 Due to being embedded inside the CPU, the TCM has a
57 the CPU and then we hang inside ITCM waiting for an
86 to have functions called locally inside the TCM without
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | inlinedata.rst | 7 data is so tiny that it readily fits inside the inode, which
10 ``inode.i_block``. If the rest of the file would fit inside the extended
|
| /linux/Documentation/hwmon/ |
| H A D | k8temp.rst | 21 This driver permits reading temperature sensor(s) embedded inside AMD K8
29 There can be up to four temperature sensors inside single CPU. The driver
|
| /linux/Documentation/devicetree/bindings/phy/ |
| H A D | phy-miphy365x.txt | 12 register offset inside the sysconfig group.
16 'reg' and 'reg-names' properties are used inside these
|
| H A D | phy-miphy28lp.txt | 14 'reg' and 'reg-names' properties are used inside these
38 different MiPHY inside the same SoC.
|
| /linux/Documentation/dev-tools/ |
| H A D | container.rst | 35 Group id to use inside the container.
54 User id to use inside the container.
97 however already be used with a relative path inside the source tree to keep
147 so that the files from the mounted volume appear to belong to id 1000 inside
203 a relative path inside the source tree::
|
| /linux/drivers/media/dvb-core/ |
| H A D | Kconfig | 63 inside the Kernel.
75 handling DVB network ULE packet loss inside the Kernel.
|
| /linux/Documentation/arch/powerpc/ |
| H A D | bootwrapper.rst | 29 tree). This image embeds a device tree blob inside
31 are all embedded inside the U-Boot uImage file format
48 inside the image instead of provided by firmware. The
75 tree blob inside the image.
|
| /linux/Documentation/filesystems/ |
| H A D | splice.rst | 8 splice is a method for moving blocks of data around inside the kernel,
|
| /linux/drivers/phy/ralink/ |
| H A D | Kconfig | 20 This option enables support for the Ralink USB PHY found inside
|
| /linux/kernel/trace/rv/monitors/sts/ |
| H A D | Kconfig | 14 * switches only happen inside the scheduler
|
| /linux/Documentation/userspace-api/media/mediactl/ |
| H A D | media.h.rst.exceptions | 3 # All symbols are mapped inside MC C domain namespace
|
| /linux/Documentation/driver-api/ |
| H A D | men-chameleon-bus.rst | 106 inside the carrier and is intended to be passed to ioremap() and friends. It
115 otherwise the IRQ number inside the Chameleon table will be returned. This
125 device ids which identify the IP Core inside the FPGA. The driver structure
|
| /linux/arch/riscv/kvm/ |
| H A D | Kconfig | 12 other operating systems inside virtual machines (guests).
|
| /linux/Documentation/networking/ |
| H A D | iso15765-2.rst | 43 the CAN payload; both the CAN ID and the byte inside the payload shall be
54 inside one single CAN message or not, also considering the overhead the protocol
208 * ``frame_txtime``: frame transmission time (defined as N_As/N_Ar inside the
314 The ISO-TP stack contained inside the Linux kernel supports the multi-frame
384 More complete (and complex) examples can be found inside the ``isotp*`` userland
|