Home
last modified time | relevance | path

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

123

/linux/drivers/mtd/ubi/
H A Dkapi.c440 * If the volume is damaged because of an interrupted update this function just
531 * If the volume is damaged because of an interrupted update this function just
617 * If the volume is damaged because of an interrupted update this function just
678 * case of failure. If the volume is damaged because of an interrupted update
713 * damaged because of an interrupted update, %-EBADMSG if the logical
752 * error code in case of failure. If the volume is damaged because of an
H A Dcdev.c126 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()
H A Dupd.c21 * treated as damaged and most I/O operations are prohibited. Only a new update
/linux/arch/sh/include/cpu-sh2/cpu/
H A Dwatchdog.h58 * Note: Due to the brain-damaged nature of this register, in sh_wdt_write_rstcsr()
/linux/Documentation/devicetree/bindings/leds/backlight/
H A Dcommon.yaml32 that a LED can be made so bright that it gets damaged or causes damage
/linux/include/linux/mtd/
H A 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
/linux/tools/testing/selftests/sync/
H A Dsync_stress_parallelism.c62 "Counter got damaged!\n"); in test_stress_two_threads_shared_timeline_thread()
/linux/arch/sparc/include/asm/
H A Dswift.h11 /* Swift is so brain damaged, here is the mmu control register. */
/linux/Documentation/power/
H A Dfreezing-of-tasks.rst117 1. The principal reason is to prevent filesystems from being damaged after
124 from the image (otherwise the filesystems will be damaged in a nasty way,
/linux/drivers/gpu/drm/mcde/
H A 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
/linux/Documentation/filesystems/
H A Docfs2.rst81 filesystem will not be damaged though, thanks to the
H A Dhpfs.rst39 misidentified and damaged under some circumstances.
327 could be damaged
/linux/drivers/usb/host/
H A Duhci-platform.c168 * This routine may be called in a damaged or failing kernel. Hence we
H A Duhci-pci.c160 * This routine may be called in a damaged or failing kernel. Hence we
/linux/scripts/dtc/libfdt/
H A Dfdt_overlay.c1083 * The overlay has been damaged, erase its magic. in fdt_overlay_apply()
1091 * The overlay might have been damaged, erase its magic. in fdt_overlay_apply()
1096 * The base device tree might have been damaged, erase its in fdt_overlay_apply()
/linux/drivers/pnp/pnpacpi/
H A Dcore.c271 /* clear out the damaged flags */ in pnpacpi_add_device()
/linux/Documentation/networking/
H A D6pack.rst42 Damaged packets that the TNC has received from the PC are not transmitted.
H A Dudplite.rst10 (video, VoIP) over wireless networks, as partly damaged packets can still be
/linux/drivers/net/ethernet/netronome/nfp/nfpcore/
H A Dnfp_mutex.c278 /* Verify that the lock marker is not damaged */ in nfp_cpp_mutex_trylock()
/linux/Documentation/devicetree/bindings/leds/
H A Dcommon.yaml168 It could happen that an LED is made so bright that it gets damaged or
/linux/drivers/net/wireless/intersil/p54/
H A Deeprom.c206 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()
/linux/drivers/net/wireless/ath/carl9170/
H A Dfw.c415 dev_err(&ar->udev->dev, "damaged firmware (%d).\n", err); in carl9170_parse_firmware()
/linux/fs/ceph/
H A Dmdsmap.c361 /* damaged */ in ceph_mdsmap_decode()
/linux/drivers/pnp/pnpbios/
H A Dcore.c329 /* clear out the damaged flags */ in insert_device()
/linux/drivers/acpi/
H A DKconfig348 may be damaged without it.

123