Home
last modified time | relevance | path

Searched full:damaged (Results 1 – 25 of 111) sorted by relevance

12345

/kernel/linux/linux-5.10/drivers/mtd/ubi/
Dkapi.c419 * If the volume is damaged because of an interrupted update this function just
510 * If the volume is damaged because of an interrupted update this function just
596 * If the volume is damaged because of an interrupted update this function just
657 * case of failure. If the volume is damaged because of an interrupted update
692 * damaged because of an interrupted update, %-EBADMSG if the logical
731 * error code in case of failure. If the volume is damaged because of an
/kernel/linux/linux-4.19/drivers/mtd/ubi/
Dkapi.c432 * If the volume is damaged because of an interrupted update this function just
523 * If the volume is damaged because of an interrupted update this function just
609 * If the volume is damaged because of an interrupted update this function just
670 * case of failure. If the volume is damaged because of an interrupted update
705 * damaged because of an interrupted update, %-EBADMSG if the logical
744 * error code in case of failure. If the volume is damaged because of an
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/backlight/
Dcommon.yaml32 that a LED can be made so bright that it gets damaged or causes damage
/kernel/linux/linux-4.19/arch/sh/include/cpu-sh2/cpu/
Dwatchdog.h61 * Note: Due to the brain-damaged nature of this register, in sh_wdt_write_rstcsr()
/kernel/linux/linux-5.10/arch/sh/include/cpu-sh2/cpu/
Dwatchdog.h58 * Note: Due to the brain-damaged nature of this register, in sh_wdt_write_rstcsr()
/kernel/linux/linux-5.10/include/linux/mtd/
Dubi.h67 * is set, the contents of the volume is certainly damaged and a new volume
74 * o the @upd_marker field means that the volume is damaged because of an
/kernel/linux/linux-5.10/arch/arm/mach-s3c/
Dpm-s3c2412.c81 * get damaged during wakeup */
/kernel/linux/linux-4.19/arch/arm/mach-s3c24xx/
Dpm-s3c2412.c81 * get damaged during wakeup */
/kernel/linux/linux-4.19/fs/ntfs/
DKconfig66 damaged someones data so we assume it is perfectly safe to use.
/kernel/linux/linux-5.10/fs/ntfs/
DKconfig66 damaged someones data so we assume it is perfectly safe to use.
/kernel/linux/linux-4.19/include/linux/mtd/
Dubi.h80 * is set, the contents of the volume is certainly damaged and a new volume
87 * o the @upd_marker field means that the volume is damaged because of an
/kernel/linux/linux-5.10/tools/testing/selftests/sync/
Dsync_stress_parallelism.c62 "Counter got damaged!\n"); in test_stress_two_threads_shared_timeline_thread()
/kernel/linux/linux-4.19/tools/testing/selftests/sync/
Dsync_stress_parallelism.c62 "Counter got damaged!\n"); in test_stress_two_threads_shared_timeline_thread()
/kernel/linux/linux-4.19/arch/sparc/include/asm/
Dswift.h11 /* Swift is so brain damaged, here is the mmu control register. */
/kernel/linux/linux-5.10/arch/sparc/include/asm/
Dswift.h11 /* Swift is so brain damaged, here is the mmu control register. */
/kernel/linux/linux-4.19/Documentation/power/
Dfreezing-of-tasks.txt99 1. The principal reason is to prevent filesystems from being damaged after
106 the image (otherwise the filesystems will be damaged in a nasty way, usually
/kernel/linux/linux-5.10/Documentation/power/
Dfreezing-of-tasks.rst106 1. The principal reason is to prevent filesystems from being damaged after
113 from the image (otherwise the filesystems will be damaged in a nasty way,
/kernel/linux/linux-4.19/Documentation/filesystems/
Docfs2.txt71 filesystem will not be damaged though, thanks to the
Dhpfs.txt31 misidentified and damaged under some circumstances.
276 could be damaged
/kernel/linux/linux-5.10/scripts/dtc/libfdt/
Dfdt_overlay.c863 * The overlay has been damaged, erase its magic. in fdt_overlay_apply()
871 * The overlay might have been damaged, erase its magic. in fdt_overlay_apply()
876 * The base device tree might have been damaged, erase its in fdt_overlay_apply()
/kernel/linux/linux-5.10/drivers/gpu/drm/mcde/
Dmcde_drv.c47 * - Enabled damaged rectangles using drm_plane_enable_fb_damage_clips()
48 * so we can selectively just transmit the damaged area to a
/kernel/linux/linux-4.19/drivers/usb/host/
Duhci-platform.c166 * This routine may be called in a damaged or failing kernel. Hence we
Duhci-grlib.c168 * This routine may be called in a damaged or failing kernel. Hence we
/kernel/linux/linux-5.10/Documentation/filesystems/
Docfs2.rst81 filesystem will not be damaged though, thanks to the
/kernel/linux/linux-5.10/drivers/usb/host/
Duhci-grlib.c168 * This routine may be called in a damaged or failing kernel. Hence we

12345