Searched refs:didn (Results 1 – 25 of 102) sorted by relevance
12345
| /linux-5.19.10/fs/affs/ |
| D | Changes | 171 - 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-5.19.10/Documentation/ABI/testing/ |
| D | sysfs-devices-platform-stratix10-rsu | 107 0 the first stage bootloader didn't run or
108 didn't reach the point of launching second
110 1 failed in second bootloader or didn't get
|
| D | sysfs-devices-platform-ipmi | 140 hosed_count (RO) Number of times the hardware didn't
207 hosed (RO) Number of times the hardware didn't
|
| /linux-5.19.10/arch/arm64/mm/ |
| D | trans_pgd-asm.S | 64 # Check the trans_pgd_stub_vectors didn't overflow
|
| /linux-5.19.10/Documentation/powerpc/ |
| D | mpc52xx.rst | 38 so. I didn't took 5xxx because there's apparently a lot of 5xxx that have
|
| /linux-5.19.10/arch/mips/include/asm/xtalk/ |
| D | xwidget.h | 236 unsigned didn:4; member
|
| /linux-5.19.10/drivers/gpu/drm/amd/display/ |
| D | TODO | 22 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-5.19.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | loongson,liointc.yaml | 62 If a CPU interrupt line didn't connect with liointc, then keep its
|
| /linux-5.19.10/Documentation/parisc/ |
| D | debugging.rst | 30 than __PAGE_OFFSET (0x10000000) which mean a virtual address didn't
|
| /linux-5.19.10/Documentation/crypto/ |
| D | descore-readme.rst | 123 crypt function and i didn't feel like ripping it out and measuring
173 man pages either didn't exist or dumped core. i had heard of kerberos,
178 (i.e. the author didn't sit down and think before coding),
191 by the larger table size. in his case he didn't realize you don't need to keep
197 to crypt(3) in his tables - i didn't check.
211 of what i didn't want to do; all their endedness-specific ``optimizations``
|
| /linux-5.19.10/Documentation/networking/device_drivers/ethernet/dec/ |
| D | dmfe.rst | 23 didn't compile this driver as a module, it will automatically load itself on boot and print a
|
| /linux-5.19.10/Documentation/scheduler/ |
| D | sched-arch.rst | 69 Possible arch problems I found (and either tried to fix or didn't):
|
| /linux-5.19.10/fs/btrfs/ |
| D | Kconfig | 107 reference problems or verifying they didn't break something.
|
| /linux-5.19.10/Documentation/userspace-api/media/v4l/ |
| D | v4l2grab.c.rst | 83 printf("Libv4l didn't accept RGB24 format. Can't proceed.\n");
|
| /linux-5.19.10/Documentation/maintainer/ |
| D | pull-requests.rst | 68 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-5.19.10/Documentation/admin-guide/mm/damon/ |
| D | reclaim.rst | 33 DAMON_RECLAIM finds memory regions that didn't accessed for specific time
36 out memory regions that didn't accessed longer time first. System
|
| /linux-5.19.10/Documentation/networking/ |
| D | arcnet.rst | 10 and cabling information if you're like many of us and didn't happen to get a
27 didn't even have to install the patch. <sigh>
53 Avery, because I didn't want to completely rewrite it.
278 don't know why the defaults on the Amiga didn't work; write to me if
452 to the Internet through freedom. If you didn't know how to do the above,
|
| /linux-5.19.10/Documentation/hwmon/ |
| D | adm1021.rst | 150 didn't have these sensors. Next generations of Xeon processors (533 MHz
|
| /linux-5.19.10/security/keys/ |
| D | Kconfig | 29 call that didn't upcall to the kernel to be cached temporarily in the
|
| /linux-5.19.10/Documentation/i2c/ |
| D | fault-codes.rst | 90 of a transfer didn't get an ACK. While it might just mean
|
| /linux-5.19.10/Documentation/process/ |
| D | handling-regressions.rst | 603 maybe it worked because the user didn't notice - again, it doesn't
619 MUCH BIGGER bug by "fixing" something that the user clearly didn't
702 regressions" kernel rule means. The reverted commit didn't change any
703 API's, and it didn't introduce any new bugs. But it ended up exposing
709 The problem was really pre-existing, and it just didn't happen to
|
| /linux-5.19.10/arch/arm/mach-davinci/ |
| D | Kconfig | 229 bool "Warn about pins the bootloader didn't set up"
|
| /linux-5.19.10/arch/mips/include/asm/pci/ |
| D | bridge.h | 275 u32 didn:4, /* Destination ID */ member
|
| /linux-5.19.10/Documentation/ia64/ |
| D | serial.rst | 31 and "console=" arguments. Without an HCDP, device names didn't
|
| /linux-5.19.10/Documentation/driver-api/usb/ |
| D | dma.rst | 25 - "usbcore" will map this DMA address, if a DMA-aware driver didn't do
|
12345