Searched refs:remnant (Results 1 – 7 of 7) sorted by relevance
4 the CFLAGS and LIBS are wrong (perhaps a remnant of the pre-imlib2
104 # Remove any remnant variable references left behind by the expansion
1814 s8 *remnant = &pwr_param->pwr_remnant; in rtw_get_tx_power_params() local1836 *remnant = (rate <= DESC_RATE11M ? dm_info->txagc_remnant_cck : in rtw_get_tx_power_params()
1103 remnant). On a 64-bit system, this is about 40 bytes per entry;1108 Note that, in a given stack frame, the path remnant (``name``) is not1109 part of the symlink that the other fields refer to. It is the remnant
838 The term "autosuspend" is an historical remnant. It doesn't mean that the
11771 This header is a truly ancient remnant of the SGI SI code, which used39097 We don't define HAVE_UDEV, that's a remnant from xf86-video-modesetting.71013 These were an unused remnant of earlier MPX work; their only users got111118 It's RAC remnant. This was substituted by xf86VGAarbiter{Lock, Unlock}116347 This is RAC's remnant. Any sane person would use a more wise method of
107070100A8AEB0000041ED0000000000000000000000116841B48100000000000000FD0000000200000000000000000000000200000000.07070100A8B07C000081A40000000000000000000000016841263500000000000000FD0000000200000000000000000000000900000000.gitkeep07070100A8B07D000081A40000000000000000000000016841263500000000000000FD0000000200000000000000000000000B00000000.skip_fsck07070100A8AEB10000A1FF0000000000000000000000016841B0B600000007000000FD0000000200000000000000000000000400000000binusr/bin07070100A8B07E000081A400000000000000000000000168412635000001CC000000FD0000000200000000000000000000001100000000busybox. ...