Home
last modified time | relevance | path

Searched refs:just (Results 1 – 25 of 1623) sorted by relevance

12345678910>>...65

/openbmc/linux/scripts/coccinelle/misc/
H A Dwarn.cocci35 cocci.print_main("printk + WARN_ON can be just WARN",p)
41 msg = "SUGGESTION: printk + WARN_ON can be just WARN"
84 cocci.print_main("printk + WARN_ON_ONCE can be just WARN_ONCE",p)
90 msg = "SUGGESTION: printk + WARN_ON_ONCE can be just WARN_ONCE"
/openbmc/linux/Documentation/userspace-api/media/rc/
H A Dlirc-get-features.rst45 Unused. Kept just to avoid breaking uAPI.
51 Unused. Kept just to avoid breaking uAPI.
68 Unused. Kept just to avoid breaking uAPI.
144 Unused. Kept just to avoid breaking uAPI.
160 Unused. Kept just to avoid breaking uAPI.
167 Unused. Kept just to avoid breaking uAPI.
/openbmc/linux/Documentation/admin-guide/
H A Dcputopology.rst46 7) topology_sibling_cpumask: just the given CPU
47 8) topology_core_cpumask: just the given CPU
48 9) topology_cluster_cpumask: just the given CPU
49 10) topology_die_cpumask: just the given CPU
50 11) topology_book_cpumask: just the given CPU
51 12) topology_drawer_cpumask: just the given CPU
/openbmc/u-boot/board/phytec/pfla02/
H A DKconfig13 bool "DRAM on just one bank"
15 activate, if the module has just one bank
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/vk-gl-cts/files/
H A Dfix-clang-private-operator.patch7 int numCalls; // just an interesting statistic
8 size_t totalBytes; // just an interesting statistic
/openbmc/linux/arch/xtensa/lib/
H A Dstrnlen_user.S101 # NOTE that in several places below, we point to the byte just after
107 addi a4, a4, 1 # point just beyond zero byte
111 addi a4, a4, 1+1 # point just beyond zero byte
115 addi a4, a4, 2+1 # point just beyond zero byte
131 addi a4, a4, 3+1 # point just beyond zero byte
/openbmc/openbmc/poky/documentation/dev-manual/
H A Ddevelopment-shell.rst6 When debugging certain commands or even when just editing packages,
14 ``configure`` and ``make``. The commands execute just as if the
57 the task just as it would be run using the ``bitbake -c`` command.
64 must be called just as BitBake would call them. That means you need to
75 instead of just using ``gcc``. The same applies to other
/openbmc/linux/Documentation/process/
H A Dmanagement-style.rst62 can be made small by just always making sure that if you were wrong (and
70 Thus the key to avoiding big decisions becomes to just avoiding to do
73 is just pitiful.
80 back-tracking is very easy: just tell everybody that you were an
94 too, and while the actual **work** was easy enough to undo by just
100 Happily, both of these reasons can be mitigated effectively by just
124 we just do both?" and look pitiful. Trust me, it works. If it's not
127 situation that they just give up.
144 as easy to undo personality disorders. You just have to live with
154 There's just a few simple rules here:
[all …]
/openbmc/openbmc/poky/meta/recipes-connectivity/ppp/ppp/
H A Dppp_on_boot7 # with just "#!/bin/sh", the commands below will be executed instead.
16 # Additional connections, which would just use settings from
/openbmc/sdbusplus/test/async/
H A Dcontext.cpp18 ctx->spawn(stdexec::just() | in spawnStop()
38 ctx->spawn(stdexec::just()); in TEST_F()
83 co_return co_await stdexec::just(0); in TEST_F() member in TEST_F::_::one::stdexec
/openbmc/linux/Documentation/mm/
H A Dactive_mm.rst25 > discussed on the mailing lists---I just returned from vacation and
33 anonymous address space we just leave the previous address space
74 more. "init_mm" should be considered just a "lazy context when no other
75 context is available", and in fact it is mainly used just at bootup when
80 should generally just do
88 Anyway, I put a pre-patch-2.3.13-1 on ftp.kernel.org just a moment ago,
/openbmc/openbmc/meta-yadro/recipes-phosphor/ipmi/phosphor-ipmi-host/
H A D0001-Add-support-for-persistent-only-settings.patch48 + // On the contrary, if there is just one object, that may mean
51 + // That is not an error, just return the regular setting.
52 + // If there's just one object, that's the only kind of setting
53 + // mode this interface supports, so just return that setting path.
/openbmc/openbmc/poky/meta/recipes-extended/unzip/unzip/
H A Dfix-security-format.patch28 if (no_endsig_found) { /* just to make sure */
52 ) { /* just to make sure again */
70 if (memcmp(G.sig, end_central_sig, 4)) { /* just to make sure again */
92 ) { /* just to make sure again */
/openbmc/openbmc/poky/meta/recipes-extended/pam/libpam/pam.d/
H A Dcommon-session15 # this avoids us returning an error just because nothing sets a success code
16 # since the modules above will each just jump around
H A Dcommon-session-noninteractive15 # this avoids us returning an error just because nothing sets a success code
16 # since the modules above will each just jump around
H A Dcommon-auth15 # this avoids us returning an error just because nothing sets a success code
16 # since the modules above will each just jump around
H A Dcommon-password20 # this avoids us returning an error just because nothing sets a success code
21 # since the modules above will each just jump around
/openbmc/openbmc/meta-phosphor/recipes-extended/pam/libpam/pam.d/
H A Dcommon-session15 # this avoids us returning an error just because nothing sets a success code
16 # since the modules above will each just jump around
/openbmc/openbmc/poky/meta/recipes-support/libical/libical/
H A D0001-cmake-Do-not-export-CC-into-gir-compiler.patch7 compiler rather than just CC variable, therefore let it use the default
8 values from environment and not synthesize it from CMAKE_C_COMPILER just
/openbmc/linux/Documentation/leds/
H A Dleds-cht-wcove.rst35 This is just like how blinking works in the LED subsystem,
37 while blinking. Breathing on this hw really is just a variant
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/tftp-hpa/files/
H A Dadd-error-check-for-disk-filled-up.patch31 if (c == '\n') /* if have cr,lf then just */
35 goto skipit; /* just skip over the putc */
36 /* else just fall through and allow it */
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DGLWTPL10 It might just work or not, there is no third option.
16 0. You just DO WHATEVER YOU WANT TO as long as you NEVER LEAVE A
/openbmc/linux/tools/memory-model/litmus-tests/
H A DZ6.0+pooncerelease+poacquirerelease+fencembonceonce.litmus10 * is a write-to-write link (AKA a "coherence" or just "co" link) and P2()
11 * to P0() is a read-to-write link (AKA a "from-reads" or just "fr" link).
/openbmc/linux/Documentation/scheduler/
H A Dsched-stats.rst111 cpu was just becoming idle
113 load did not require balancing when the cpu was just becoming idle
115 tasks and failed, when the cpu was just becoming idle
117 load_balance() in this domain when the cpu was just becoming idle
120 target task was cache-hot when just becoming idle
122 find a busier queue while the cpu was just becoming idle
124 was just becoming idle but no busier group was found
/openbmc/linux/Documentation/ABI/stable/
H A Dsysfs-firmware-opal-elog47 Currently just "0x00 PEL" - platform error log.
52 <16kb, often just hundreds of bytes and
61 operations (currently just acknowledge).

12345678910>>...65