Searched full:ideally (Results 1 – 25 of 422) sorted by relevance
12345678910>>...17
| /linux-6.14.4/include/trace/events/ |
| D | ipi.h | 105 * __tracepoint_string, ideally the same as used with trace_ipi_raise
121 * __tracepoint_string, ideally the same as used with trace_ipi_raise for
|
| /linux-6.14.4/arch/x86/include/asm/ |
| D | emulate_prefix.h | 7 * ideally these would decode to 'whole' instruction and not destroy
|
| /linux-6.14.4/tools/arch/x86/include/asm/ |
| D | emulate_prefix.h | 7 * ideally these would decode to 'whole' instruction and not destroy
|
| /linux-6.14.4/arch/x86/entry/vdso/vdso32/ |
| D | note.S | 11 /* Ideally this would use UTS_NAME, but using a quoted string here
|
| /linux-6.14.4/drivers/gpu/drm/panthor/ |
| D | panthor_fw.h | 282 * TODO: Ideally we'd want to use a cmpxchg() to update the req, but FW
326 * TODO: Ideally we'd want to use a cmpxchg() to update the req, but FW
370 * TODO: Ideally we'd want to use a cmpxchg() to update the req, but FW
|
| /linux-6.14.4/rust/kernel/ |
| D | device_id.rs | 24 /// Ideally, this should be achieved using a const function that does conversion instead of
31 /// Similar to the previous requirement, the data should ideally be added during `Self` to
|
| /linux-6.14.4/Documentation/devicetree/bindings/iio/frequency/ |
| D | adi,admv4420.yaml | 14 mixer with an integrated fractional-N synthesizer, ideally suited
|
| D | adi,adf4377.yaml | 16 ideally suited for data converter and mixed signal front end (MxFE) clock
|
| /linux-6.14.4/arch/arm/mach-omap2/ |
| D | powerdomains2xxx_3xxx_data.c | 27 * Ideally the DSP/IVA2 could just be the same powerdomain, but the PRCM
|
| /linux-6.14.4/Documentation/driver-api/media/ |
| D | maintainer-entry-profile.rst | 143 We may accept pure standalone style cleanups, but they should ideally
187 next merge window they should be sent before -rc5, and ideally stabilized
|
| /linux-6.14.4/Documentation/doc-guide/ |
| D | maintainer-profile.rst | 31 ideally justify who the intended target audience is somewhere in the
|
| /linux-6.14.4/drivers/gpu/drm/xe/display/ |
| D | intel_fb_bo.c | 51 * XE_BO_FLAG_SCANOUT should ideally be set at creation, or is in intel_fb_bo_framebuffer_init()
|
| /linux-6.14.4/arch/sparc/vdso/ |
| D | vdso-layout.lds.S | 52 * Ideally this would live in a C file: kept in here for
|
| /linux-6.14.4/arch/arm/mach-versatile/ |
| D | integrator.c | 87 * We need to stop things allocating the low memory; ideally we need a
|
| /linux-6.14.4/Documentation/driver-api/ |
| D | ioctl.rst | 104 Timeout values and timestamps should ideally use CLOCK_MONOTONIC time,
213 subsystems implement the same command for multiple drivers. Ideally the
|
| /linux-6.14.4/arch/openrisc/kernel/ |
| D | unwinder.c | 45 * Ideally the stack parameter will be passed as FP, but it can not be
|
| /linux-6.14.4/Documentation/nvdimm/ |
| D | maintainer-entry-profile.rst | 49 next merge window they should be sent before -rc4, and ideally
|
| /linux-6.14.4/arch/mips/include/asm/ |
| D | unroll.h | 9 * Ideally we'd rely upon the compiler to provide this but there's no commonly
|
| /linux-6.14.4/Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 47 called when the critical section ends. All that ideally along with an
|
| /linux-6.14.4/Documentation/admin-guide/pm/ |
| D | strategies.rst | 34 are inactive, ideally, they should be in low-power states in which they may not
|
| /linux-6.14.4/Documentation/networking/ |
| D | netmem.rst | 60 Ideally, drivers should not have to check the underlying netmem type via
|
| /linux-6.14.4/tools/testing/selftests/arm64/fp/ |
| D | README | 60 Ideally, the test should be allowed to run for many minutes or hours
|
| /linux-6.14.4/scripts/ |
| D | rustdoc_test_builder.rs | 5 //! This script is a hack to extract the test from `rustdoc`'s output. Ideally, `rustdoc` would
|
| /linux-6.14.4/Documentation/admin-guide/ |
| D | reporting-issues.rst | 18 ([email protected]); ideally also CC the maintainer and the mailing
122 ideally use a 'vanilla' build. Ignoring these advices will dramatically
147 reproduce the issue. Ideally, make the kernel's build configuration
196 issue and ideally explain how to reproduce it. Mention the first version
669 First look at the line 'Status'. Ideally it should be 'Supported' or
779 ideally use a 'vanilla' built. Ignoring these advices will dramatically
1074 reproduce the issue. Ideally, make the kernel's build configuration
1105 earlier that outline how you and ideally others can reproduce the issue; in
1145 report. Ideally use something where the files stay available for years, as
1267 MAINTAINERS file lists in the section 'security contact'. Ideally directly CC
[all …]
|
| /linux-6.14.4/include/net/ |
| D | ipv6_stubs.h | 20 /* This is ugly, ideally these symbols should be built
|
12345678910>>...17