| /kernel/linux/linux-5.10/tools/testing/selftests/net/forwarding/ |
| D | mirror_gre_flower.sh | 9 # addresses is configured with mirror action. It is expected that when pinging
10 # this address, mirroring takes place, whereas when pinging the other one,
|
| /kernel/linux/linux-6.6/tools/testing/selftests/net/forwarding/ |
| D | mirror_gre_flower.sh | 9 # addresses is configured with mirror action. It is expected that when pinging
10 # this address, mirroring takes place, whereas when pinging the other one,
|
| /kernel/linux/linux-6.6/drivers/watchdog/ |
| D | armada_37xx_wdt.c | 28 * while counter ID 0 is used to implement pinging the watchdog: counter ID 1 is
30 * Pinging is done by forcing immediate end count event on counter ID 0.
31 * If only one counter was used, pinging would have to be implemented by
|
| /kernel/linux/linux-5.10/drivers/watchdog/ |
| D | armada_37xx_wdt.c | 29 * while counter ID 0 is used to implement pinging the watchdog: counter ID 1 is
31 * Pinging is done by forcing immediate end count event on counter ID 0.
32 * If only one counter was used, pinging would have to be implemented by
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/watchdog/ |
| D | realtek,otto-wdt.yaml | 20 During this phase, pinging the WDT has no effect, and a reset is
|
| /kernel/linux/linux-6.6/Documentation/nvdimm/ |
| D | maintainer-entry-profile.rst | 57 In general, please wait up to one week before pinging for feedback. A
|
| /kernel/linux/linux-5.10/Documentation/nvdimm/ |
| D | maintainer-entry-profile.rst | 57 In general, please wait up to one week before pinging for feedback. A
|
| /kernel/linux/linux-6.6/arch/x86/platform/uv/ |
| D | uv_nmi.c | 598 uv_cpu_nmi_per(cpu).pinging = 1; in uv_nmi_nr_cpus_ping()
609 uv_cpu_nmi_per(cpu).pinging = 0; in uv_nmi_cleanup_mask()
944 if (!this_cpu_read(uv_cpu_nmi.pinging) && !uv_check_nmi(hub_nmi)) { in uv_handle_nmi()
1008 if (!this_cpu_read(uv_cpu_nmi.pinging)) { in uv_handle_nmi_ping()
1016 this_cpu_write(uv_cpu_nmi.pinging, 0); in uv_handle_nmi_ping()
|
| /kernel/linux/linux-5.10/arch/x86/platform/uv/ |
| D | uv_nmi.c | 598 uv_cpu_nmi_per(cpu).pinging = 1; in uv_nmi_nr_cpus_ping()
609 uv_cpu_nmi_per(cpu).pinging = 0; in uv_nmi_cleanup_mask()
947 if (!this_cpu_read(uv_cpu_nmi.pinging) && !uv_check_nmi(hub_nmi)) { in uv_handle_nmi()
1011 if (!this_cpu_read(uv_cpu_nmi.pinging)) { in uv_handle_nmi_ping()
1019 this_cpu_write(uv_cpu_nmi.pinging, 0); in uv_handle_nmi_ping()
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mfd/ |
| D | rohm,bd9576-pmic.yaml | 65 the maximum timeout. Eg. if pinging watchdog is not done within this time
|
| /kernel/linux/linux-6.6/Documentation/watchdog/ |
| D | watchdog-api.rst | 70 stop pinging the watchdog without disabling it first. This will then
78 Pinging the watchdog using an ioctl:
|
| /kernel/linux/linux-5.10/Documentation/watchdog/ |
| D | watchdog-api.rst | 70 stop pinging the watchdog without disabling it first. This will then
78 Pinging the watchdog using an ioctl:
|
| /kernel/linux/linux-5.10/arch/m68k/include/asm/ |
| D | mac_psc.h | 29 * registers and subsequently confirmed using MacsBug (ie by pinging the
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | xfs-maintainer-entry-profile.rst | 184 In general, please wait at least one week before pinging for feedback.
|
| /kernel/linux/linux-6.6/arch/m68k/include/asm/ |
| D | mac_psc.h | 29 * registers and subsequently confirmed using MacsBug (ie by pinging the
|
| /kernel/linux/linux-6.6/tools/testing/selftests/net/ |
| D | test_vxlan_under_vrf.sh | 88 # Check connectivity between HVs by pinging hv-2 from hv-1
|
| /kernel/linux/linux-5.10/tools/testing/selftests/net/ |
| D | test_vxlan_under_vrf.sh | 88 # Check connectivity between HVs by pinging hv-2 from hv-1
|
| D | ipsec.c | 1608 /* UDP pinging without xfrm */ in child_serv()
1633 /* UDP pinging with xfrm tunnel */ in child_serv()
1754 /* UDP pinging without xfrm */ in grand_child_serv()
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/cable/ |
| D | sb1000.rst | 120 10. Try pinging a site via ``ping -c 5 www.yahoo.com``, for example. You should
|
| /kernel/linux/linux-6.6/Documentation/networking/device_drivers/cable/ |
| D | sb1000.rst | 120 10. Try pinging a site via ``ping -c 5 www.yahoo.com``, for example. You should
|
| /kernel/linux/linux-6.6/drivers/media/pci/ivtv/ |
| D | ivtv-firmware.c | 93 IVTV_DEBUG_INFO("pinging (?) APU\n"); in ivtv_halt_firmware()
|
| /kernel/linux/linux-5.10/drivers/media/pci/ivtv/ |
| D | ivtv-firmware.c | 93 IVTV_DEBUG_INFO("pinging (?) APU\n"); in ivtv_halt_firmware()
|
| /kernel/linux/linux-6.6/drivers/usb/musb/ |
| D | tusb6010_omap.c | 162 * Easy to test with g_ether by pinging the MUSB board with ping -s54. in tusb_omap_dma_cb()
|
| /kernel/linux/linux-5.10/drivers/usb/musb/ |
| D | tusb6010_omap.c | 162 * Easy to test with g_ether by pinging the MUSB board with ping -s54. in tusb_omap_dma_cb()
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | maintainer-kvm-x86.rst | 77 current release cycle and have realistic expectations. If you are pinging for
|