Home
last modified time | relevance | path

Searched full:solve (Results 1 – 25 of 385) sorted by relevance

12345678910>>...16

/kernel/linux/linux-5.10/drivers/ide/
Ddtc2278.c22 * Changing this #undef to #define may solve start up problems in some systems.
124 * and may solve start-up problems for some people. in dtc2278_probe()
/kernel/linux/linux-6.6/Documentation/admin-guide/hw-vuln/
Dcore-scheduling.rst181 Open cross-HT issues that core scheduling does not solve
206 parallelism of the untrusted tasks, it would still solve the above issues while
213 to LKML to solve this, but it is debatable whether such windows are practically
/kernel/linux/linux-5.10/drivers/net/ethernet/dlink/
DKconfig51 is known to solve bugs on certain chips.
/kernel/linux/linux-6.6/drivers/net/ethernet/dlink/
DKconfig51 is known to solve bugs on certain chips.
/kernel/linux/linux-6.6/arch/powerpc/kernel/
Dsetup.h53 * tricky to solve for setup-common.c so have it here.
/kernel/linux/linux-5.10/arch/powerpc/kernel/
Dsetup.h53 * tricky to solve for setup-common.c so have it here.
/kernel/linux/linux-6.6/arch/arm64/kvm/hyp/nvhe/
Dtlb.c119 * from EL1. To solve this, we invalidate the entire I-cache when in __kvm_tlb_flush_vmid_ipa()
171 * from EL1. To solve this, we invalidate the entire I-cache when in __kvm_tlb_flush_vmid_ipa_nsh()
/kernel/linux/linux-6.6/Documentation/maintainer/
Dmodifying-patches.rst12 one submitters code and make him endorse your bugs. To solve this problem, it
/kernel/linux/linux-5.10/Documentation/maintainer/
Dmodifying-patches.rst12 one submitters code and make him endorse your bugs. To solve this problem, it
/kernel/linux/linux-6.6/Documentation/ABI/stable/
Dsysfs-firmware-opal-elog33 user space to solve the problem. In future, we may
/kernel/linux/linux-5.10/Documentation/ABI/stable/
Dsysfs-firmware-opal-elog33 user space to solve the problem. In future, we may
/kernel/linux/linux-6.6/Documentation/locking/
Drobust-futexes.rst37 To solve such types of problems, "robust mutex" userspace APIs were
54 To solve this problem, the traditional approach was to extend the vma
/kernel/linux/linux-5.10/Documentation/locking/
Drobust-futexes.rst37 To solve such types of problems, "robust mutex" userspace APIs were
54 To solve this problem, the traditional approach was to extend the vma
/kernel/linux/linux-6.6/arch/riscv/lib/
Dmemmove.S50 * Solve for some register values now.
66 * Now solve for t5 and t6.
/kernel/linux/linux-5.10/Documentation/core-api/
Didr.rst12 A common problem to solve is allocating identifiers (IDs); generally
/kernel/liteos_a/testsuites/kernel/sample/kernel_base/core/task/smp/
DIt_smp_los_task_113.c77 ret); // expect RET=LOS_ERRNO_TSK_SUSPEND_LOCKED, but can't solve asynchronous problems in Testcase()
DIt_smp_los_task_072.c77 ret); // expect RET=LOS_ERRNO_TSK_SUSPEND_LOCKED, but can't solve asynchronous problems in Testcase()
/kernel/linux/linux-6.6/Documentation/filesystems/
Dvirtiofs.rst25 solve these problems by providing file system access without networking.
/kernel/linux/linux-6.6/Documentation/networking/
Dvxlan.rst7 The VXLAN protocol is a tunnelling protocol designed to solve the
/kernel/linux/linux-6.6/Documentation/core-api/
Didr.rst12 A common problem to solve is allocating identifiers (IDs); generally
/kernel/linux/linux-5.10/Documentation/filesystems/
Dvirtiofs.rst25 solve these problems by providing file system access without networking.
/kernel/linux/linux-5.10/Documentation/networking/
Dvxlan.rst7 The VXLAN protocol is a tunnelling protocol designed to solve the
/kernel/linux/linux-5.10/drivers/net/ethernet/realtek/
DKconfig64 of PCI shared memory (MMIO). This can possibly solve some problems
/kernel/linux/linux-5.10/drivers/gpu/drm/i915/gt/uc/
Dintel_uc.h51 * To solve both these requirements, we commit to using the microcontrollers if
/kernel/linux/linux-6.6/drivers/net/ethernet/realtek/
DKconfig64 of PCI shared memory (MMIO). This can possibly solve some problems

12345678910>>...16