MAJOR=4 MINOR=26 DEVNAME=tty26 " l4( (  fB- 163 # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the net shaper infrastructure. # # Copyright (c) 2024, Red Hat, Inc. # obj-y += shaper.o shaper_nl_gen.o   File not found.  # SPDX-License-Identifier: GPL-2.0 ifeq ($(srctree),) srctree := $(patsubst %/,%,$(dir $(CURDIR))) srctree := $(patsubst %/,%,$(dir $(srctree))) endif include $(srctree)/tools//scripts/Makefile.include define allow-override $(if $(or $(findstring environment,$(origin $(1))),\ $(findstring command line,$(origin $(1)))),,\ $(eval $(1) = $(2))) endef $(call allow-override,CC,$(CROSS_COMPILE)gcc) $(call allow-override,LD,$(CROSS_COMPILE)ld) export HOSTCC HOSTLD HOSTAR ifeq ($(V),1) Q = else Q = @ endif export Q srctree CC LD MAKEFLAGS := --no-print-directory build := -f $(srctree)/tools/build/Makefile.build dir=. obj all: $(OUTPUT)fixdep # Make sure there's anything to clean, # feature contains check for existing OUTPUT TMP_O := $(if $(OUTPUT),$(OUTPUT)feature/,./) clean: $(call QUIET_CLEAN, fixdep) $(Q)find $(or $(OUTPUT),.) -name '*.o' -delete -o -name '\.*.cmd' -delete -o -name '\.*.d' -delete $(Q)rm -f $(OUTPUT)fixdep $(call QUIET_CLEAN, feature-detect) ifneq ($(wildcard $(TMP_O)),) $(Q)$(MAKE) -C feature OUTPUT=$(TMP_O) clean >/dev/null endif $(OUTPUT)fixdep: $(srctree)/tools/build/fixdep.c $(QUIET_CC)$(HOSTCC) $(KBUILD_HOSTCFLAGS) $(KBUILD_HOSTLDFLAGS) -o $@ $< #l4( (  fD- q/?# SPDX-License-Identifier: GPL-2.0-only # # Watchdog device configuration # menuconfig WATCHDOG bool "Watchdog Timer Support" help If you say Y here (and to one of the following options) and create a character special file /dev/watchdog with major number 10 and minor number 130 using mknod ("man mknod"), you will get a watchdog, i.e.: subsequently opening the file and then failing to write to it for longer than 1 minute will result in rebooting the machine. This could be useful for a networked machine that needs to come back on-line as fast as possible after a lock-up. There's both a watchdog implementation entirely in software (which can sometimes fail to reboot the machine) and a driver for hardware watchdog boards, which are more robust and can also keep track of the temperature inside your computer. For details, read in the kernel source. The watchdog is usually used together with the watchdog daemon which is available from . This daemon can also monitor NFS connections and can reboot the machine when the process table is full. If unsure, say N. if WATCHDOG config WATCHDOG_CORE tristate "WatchDog Timer Driver Core" help Say Y here if you want to use the new watchdog timer driver core. This driver provides a framework for all watchdog timer drivers and gives them the /dev/watchdog interface (and later also the sysfs interface). config WATCHDOG_NOWAYOUT bool "Disable watchdog shutdown on close" help The default watchdog behaviour (which you get if you say N here) is to stop the timer if the process managing it closes the file /dev/watchdog. It's always remotely possible that this process might get killed. If you say Y here, the watchdog cannot be stopped once it has been started. config WATCHDOG_HANDLE_BOOT_ENABLED bool "Update boot-enabled watchdog until userspace takes over" default y help The default watchdog behaviour (which you get if you say Y here) is to ping watchdog devices that were enabled before the driver has been loaded until control is taken over from userspace using the /dev/watchdog file. If you say N here, the kernel will not update the watchdog on its own. Thus if your userspace does not start fast enough your device will reboot. config WATCHDOG_OPEN_TIMEOUT int "Timeout value for opening watchdog device" default 0 help