Searched full:damaged (Results 1 – 25 of 57) sorted by relevance
123
/linux-5.10/drivers/mtd/ubi/ |
D | kapi.c | 419 * 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
|
D | cdev.c | 126 ubi_warn(vol->ubi, "update of volume %d not finished, volume is damaged", in vol_cdev_release() 189 ubi_err(vol->ubi, "damaged volume, update marker is set"); in vol_cdev_read()
|
/linux-5.10/Documentation/devicetree/bindings/leds/backlight/ |
D | common.yaml | 32 that a LED can be made so bright that it gets damaged or causes damage
|
/linux-5.10/arch/sh/include/cpu-sh2/cpu/ |
D | watchdog.h | 58 * Note: Due to the brain-damaged nature of this register, in sh_wdt_write_rstcsr()
|
/linux-5.10/include/linux/mtd/ |
D | ubi.h | 67 * 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
|
/linux-5.10/fs/ntfs/ |
D | Kconfig | 66 damaged someones data so we assume it is perfectly safe to use.
|
/linux-5.10/arch/arm/mach-s3c/ |
D | pm-s3c2412.c | 81 * get damaged during wakeup */
|
/linux-5.10/tools/testing/selftests/sync/ |
D | sync_stress_parallelism.c | 62 "Counter got damaged!\n"); in test_stress_two_threads_shared_timeline_thread()
|
/linux-5.10/arch/sparc/include/asm/ |
D | swift.h | 11 /* Swift is so brain damaged, here is the mmu control register. */
|
/linux-5.10/Documentation/power/ |
D | freezing-of-tasks.rst | 106 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,
|
/linux-5.10/scripts/dtc/libfdt/ |
D | fdt_overlay.c | 863 * 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()
|
/linux-5.10/drivers/gpu/drm/mcde/ |
D | mcde_drv.c | 47 * - Enabled damaged rectangles using drm_plane_enable_fb_damage_clips() 48 * so we can selectively just transmit the damaged area to a
|
/linux-5.10/drivers/usb/host/ |
D | uhci-grlib.c | 168 * This routine may be called in a damaged or failing kernel. Hence we
|
D | uhci-platform.c | 166 * This routine may be called in a damaged or failing kernel. Hence we
|
D | uhci-pci.c | 158 * This routine may be called in a damaged or failing kernel. Hence we
|
/linux-5.10/Documentation/filesystems/ |
D | ocfs2.rst | 81 filesystem will not be damaged though, thanks to the
|
D | hpfs.rst | 39 misidentified and damaged under some circumstances. 327 could be damaged
|
/linux-5.10/fs/xfs/scrub/ |
D | repair.c | 372 * the damaged btree, initialize a fresh btree root, and insert the records. 394 * Now that we've constructed a new btree to replace the damaged one, we want 631 * btree roots. This is not guaranteed to work if the AG is heavily damaged
|
/linux-5.10/drivers/pnp/pnpacpi/ |
D | core.c | 271 /* clear out the damaged flags */ in pnpacpi_add_device()
|
/linux-5.10/Documentation/networking/ |
D | 6pack.rst | 42 Damaged packets that the TNC has received from the PC are not transmitted.
|
D | udplite.rst | 10 (video, VoIP) over wireless networks, as partly damaged packets can still be
|
/linux-5.10/drivers/net/ethernet/netronome/nfp/nfpcore/ |
D | nfp_mutex.c | 278 /* Verify that the lock marker is not damaged */ in nfp_cpp_mutex_trylock()
|
/linux-5.10/drivers/net/wireless/ath/carl9170/ |
D | fw.c | 415 dev_err(&ar->udev->dev, "damaged firmware (%d).\n", err); in carl9170_parse_firmware()
|
/linux-5.10/fs/ceph/ |
D | mdsmap.c | 359 /* damaged */ in ceph_mdsmap_decode()
|
/linux-5.10/drivers/net/wireless/intersil/p54/ |
D | eeprom.c | 206 wiphy_err(dev->wiphy, "Disabling totally damaged %d GHz band\n", in p54_generate_band() 331 "Unsupported or damaged EEPROM detected. " in p54_generate_channel_lists()
|
123