Home
last modified time | relevance | path

Searched refs:didn (Results 1 – 25 of 95) sorted by relevance

1234

/Linux-v5.4/fs/affs/
DChanges171 - getblock() didn't update the lastblock field in the
192 zone number was zero, the loop didn't terminate,
200 affs use it on a 68k, they didn't notice. But why did
214 invalid filenames didn't work correctly.
224 can be trapped. Previously, ro remounts didn't
225 flush the super block, and rw remounts didn't
249 - truncate() didn't allocate an extension block
316 - Fixed a nasty bug which didn't allow read-only
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-devices-platform-stratix10-rsu105 0 the first stage bootloader didn't run or
106 didn't reach the point of launching second
108 1 failed in second bootloader or didn't get
Dsysfs-devices-platform-ipmi139 hosed_count: (RO) Number of times the hardware didn't
204 hosed: (RO) Number of times the hardware didn't
/Linux-v5.4/arch/arc/include/asm/
Dtlb-mmu1.h27 ; didn't want to change setup.c
/Linux-v5.4/Documentation/powerpc/
Dmpc52xx.rst38 so. I didn't took 5xxx because there's apparently a lot of 5xxx that have
Deeh-pci-error-recovery.rst304 network daemons and file systems that didn't need to be disturbed.
308 network daemons, that didn't need to even know that the pci
/Linux-v5.4/arch/mips/include/asm/xtalk/
Dxwidget.h236 unsigned didn:4; member
/Linux-v5.4/Documentation/crypto/
Ddescore-readme.txt98 crypt function and i didn't feel like ripping it out and measuring
138 man pages either didn't exist or dumped core. i had heard of kerberos,
143 (i.e. the author didn't sit down and think before coding),
156 by the larger table size. in his case he didn't realize you don't need to keep
162 to crypt(3) in his tables - i didn't check.
175 of what i didn't want to do; all their endedness-specific `optimizations'
/Linux-v5.4/drivers/gpu/drm/amd/display/
DTODO22 I haven't looked recently but I didn't get the impression there was a
93 18. There's a pile of sink handling code, both for DP and HDMI where I didn't
/Linux-v5.4/Documentation/parisc/
Ddebugging.rst30 than __PAGE_OFFSET (0x10000000) which mean a virtual address didn't
/Linux-v5.4/Documentation/networking/device_drivers/dec/
Ddmfe.txt18 didn't compile this driver as a module, it will automatically load itself on boot and print a
/Linux-v5.4/Documentation/scheduler/
Dsched-arch.rst69 Possible arch problems I found (and either tried to fix or didn't):
/Linux-v5.4/fs/btrfs/
DKconfig102 reference problems or verifying they didn't break something.
/Linux-v5.4/Documentation/media/uapi/v4l/
Dv4l2grab.c.rst90 printf("Libv4l didn't accept RGB24 format. Can't proceed.\\n");
/Linux-v5.4/Documentation/maintainer/
Dpull-requests.rst68 diffstat anyway, and if you didn't mention it, I'll just be extra
72 happened that this didn't go through the merge window..
/Linux-v5.4/security/keys/
DKconfig33 call that didn't upcall to the kernel to be cached temporarily in the
/Linux-v5.4/Documentation/networking/
Darcnet.txt3 and cabling information if you're like many of us and didn't happen to get a
20 didn't even have to install the patch. <sigh>
53 Avery, because I didn't want to completely rewrite it.
257 don't know why the defaults on the Amiga didn't work; write to me if
418 to the Internet through freedom. If you didn't know how to do the above,
/Linux-v5.4/Documentation/hwmon/
Dadm1021.rst150 didn't have these sensors. Next generations of Xeon processors (533 MHz
/Linux-v5.4/arch/arm/mach-omap1/
DKconfig54 bool "Warn about pins the bootloader didn't set up"
/Linux-v5.4/Documentation/i2c/
Dfault-codes.rst90 of a transfer didn't get an ACK. While it might just mean
/Linux-v5.4/arch/mips/include/asm/pci/
Dbridge.h275 u32 didn:4, /* Destination ID */ member
/Linux-v5.4/arch/arm/mach-davinci/
DKconfig232 bool "Warn about pins the bootloader didn't set up"
/Linux-v5.4/Documentation/ia64/
Dserial.rst31 and "console=" arguments. Without an HCDP, device names didn't
/Linux-v5.4/Documentation/driver-api/usb/
Ddma.rst25 - "usbcore" will map this DMA address, if a DMA-aware driver didn't do
/Linux-v5.4/Documentation/admin-guide/gpio/
Dsysfs.rst83 it was exported by kernel code that didn't explicitly

1234