Home
last modified time | relevance | path

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

12345678910>>...136

/linux-6.3-rc2/Documentation/arm64/
A Delf_hwcaps.rst53 Functionality implied by idreg.field == val.
70 Functionality implied by ID_AA64PFR0_EL1.FP == 0b0000.
80 Functionality implied by ID_AA64ISAR0_EL1.AES == 0b0001.
83 Functionality implied by ID_AA64ISAR0_EL1.AES == 0b0010.
98 Functionality implied by ID_AA64PFR0_EL1.FP == 0b0001.
134 Functionality implied by ID_AA64ISAR0_EL1.DP == 0b0001.
165 ID_AA64ISAR1_EL1.API == 0b0001, as described by
170 ID_AA64ISAR1_EL1.GPI == 0b0001, as described by
229 by Documentation/arm64/memory-tagging-extension.rst.
242 by Documentation/arm64/memory-tagging-extension.rst.
[all …]
/linux-6.3-rc2/Documentation/translations/zh_CN/process/
A Dsubmitting-patches.rst336 何时使用Acked-by:，CC:，和Co-Developed by:
342 那么他们可以要求在补丁的变更日志中添加一个Acked-by:。
350 Acked-by：不一定表示对整个补丁的确认。例如，如果一个补丁影响多个子系统，并且
362 过From:还是Co-developed-by:表明。值得注意的是，最后一个Singed-off-by:必须是
390 使用Reported-by:、Tested-by:、Reviewed-by:、Suggested-by:和Fixes:
397 Tested-by: 标签表示补丁已由指定的人（在某些环境中）成功测试。这个标签通知
400 Reviewed-by：根据审阅者的监督声明，表明该补丁已被审阅并被认为是可接受的：
406 通过提供我的Reviewed-by:标签，我声明：
427 一旦从测试人员或审阅者的“Tested-by”和“Reviewed-by”标签出现在邮件列表中，
468 - 上述的 ``Signed-off-by:`` 行，也将出现在更改日志中。
[all …]
A D5.Posting.rst125 - 一个或多个标记行，至少有一个由补丁作者的 Signed-off-by 签名。标记将在下面
163 - Signed-off-by: 这是一个开发人员的证明，证明他或她有权提交补丁以包含到内核
168 - Co-developed-by: 声明补丁是由多个开发人员共同创建的；当几个人在一个补丁上
170 Co-developed-by: 表示作者身份，所以每个共同开发人，必须紧跟在相关合作作者
171 的Signed-off-by之后。具体内容和示例见以下文件
174 - Acked-by: 表示另一个开发人员（通常是相关代码的维护人员）同意补丁适合包含
177 - Tested-by: 声明某人已经测试了补丁并确认它可以工作。
179 - Reviewed-by: 表示某开发人员已经审查了补丁的正确性；有关详细信息，请参阅
182 - Reported-by: 指定报告此补丁修复的问题的用户；此标记用于表示感谢。
/linux-6.3-rc2/Documentation/translations/zh_TW/process/
A Dsubmitting-patches.rst385 12）何時使用Acked-by:，CC:，和Co-Developed by:
391 那麼他們可以要求在補丁的變更日誌中添加一個 Acked-by:
393 Acked-by：通常由受影響代碼的維護者使用，當該維護者既沒有貢獻也沒有轉發補丁時。
395 Acked-by: 不像簽字人那樣正式。這是一個記錄，確認人至少審查了補丁，並表示接受。
399 Acked-by：不一定表示對整個補丁的確認。例如，如果一個補丁影響多個子系統，並且
446 Tested-by: 標記表示補丁已由指定的人（在某些環境中）成功測試。這個標籤通知
450 Reviewed-by：相反，根據審查人的聲明，表明該補丁已被審查並被認爲是可接受的：
456 通過提供我的 Reviewed-by，我聲明：
472 問題。任何感興趣的審閱者（完成工作的人）都可以爲一個補丁提供一個 Review-by
474 Reviewed-by: 當由已知了解主題區域並執行徹底檢查的審閱者提供時，通常會增加
[all …]
A D5.Posting.rst128 - 一個或多個標記行，至少有一個由補丁作者的 Signed-off-by 簽名。標記將在下面
166 - Signed-off-by: 這是一個開發人員的證明，證明他或她有權提交補丁以包含到內核
171 - Co-developed-by: 聲明補丁是由多個開發人員共同創建的；當幾個人在一個補丁上
173 Co-developed-by: 表示作者身份，所以每個共同開發人，必須緊跟在相關合作作者
174 的Signed-off-by之後。具體內容和示例見以下文件
177 - Acked-by: 表示另一個開發人員（通常是相關代碼的維護人員）同意補丁適合包含
180 - Tested-by: 聲明某人已經測試了補丁並確認它可以工作。
182 - Reviewed-by: 表示某開發人員已經審查了補丁的正確性；有關詳細信息，請參閱
185 - Reported-by: 指定報告此補丁修復的問題的用戶；此標記用於表示感謝。
/linux-6.3-rc2/Documentation/translations/ja_JP/
A DSubmittingPatches346 Signed-off-by とあなたがその末尾に追加する Signed-off-by の間に、修正を
382 13) いつ Acked-by: と Cc: を使うのか
388 る承認を記録し、示したいとします。その場合、その人を示すのに Acked-by: が使
389 えます。Acked-by: はパッチのチェンジログにも追加されます。
392 の伝播パスにいなかった時にも、メンテナは Acked-by: をしばしば利用します。
394 Acked-by: は Signed-off-by: のように公式なタグではありません。それはメンテナが
397 Acked-by: へ置き換えることがあります。
401 のメンテナからの Acked-by: を持っているとします。その場合、Acked-by: は通常
403 この点は、ご自分で判断してください。(その Acked-by: が)疑わしい場合は、
412 14) Reported-by:, Tested-by:, Reviewed-by: および Suggested-by: の利用
[all …]
/linux-6.3-rc2/arch/arm/boot/dts/
A Daxm5516-cpus.dtsi77 cpu-release-addr = <0>; // Fixed by the boot loader
85 cpu-release-addr = <0>; // Fixed by the boot loader
93 cpu-release-addr = <0>; // Fixed by the boot loader
101 cpu-release-addr = <0>; // Fixed by the boot loader
109 cpu-release-addr = <0>; // Fixed by the boot loader
117 cpu-release-addr = <0>; // Fixed by the boot loader
125 cpu-release-addr = <0>; // Fixed by the boot loader
133 cpu-release-addr = <0>; // Fixed by the boot loader
141 cpu-release-addr = <0>; // Fixed by the boot loader
149 cpu-release-addr = <0>; // Fixed by the boot loader
[all …]
A Dexynos5420-cpus.dtsi15 * booting cluster (big or LITTLE) is chosen by IROM code by reading
65 #cooling-cells = <2>; /* min followed by max */
77 #cooling-cells = <2>; /* min followed by max */
89 #cooling-cells = <2>; /* min followed by max */
101 #cooling-cells = <2>; /* min followed by max */
113 #cooling-cells = <2>; /* min followed by max */
125 #cooling-cells = <2>; /* min followed by max */
137 #cooling-cells = <2>; /* min followed by max */
149 #cooling-cells = <2>; /* min followed by max */
/linux-6.3-rc2/arch/x86/crypto/
A Daes_ctrby8_avx-x86_64.S174 .rept by
189 .rept by
206 .rept by
220 .rept by
240 .rept by
249 .rept by
269 .rept by
284 .rept by
298 .rept by
314 .rept by
[all …]
/linux-6.3-rc2/arch/arm/nwfpe/
A Dsoftfloat-macros8 Written by John R. Hauser. This work was made possible in part by the
39 The result is stored in the location pointed to by `zPtr'.
64 The result is stored in the location pointed to by `zPtr'.
87 Shifts the 128-bit value formed by concatenating `a0' and `a1' right by 64
134 Shifts the 128-bit value formed by concatenating `a0' and `a1' right by the
167 Shifts the 128-bit value formed by concatenating `a0' and `a1' right by the
174 the locations pointed to by `z0Ptr' and `z1Ptr'.
282 Shifts the 128-bit value formed by concatenating `a0' and `a1' left by the
341 are stored at the locations pointed to by `z0Ptr' and `z1Ptr'.
420 pointed to by `z0Ptr', `z1Ptr', and `z2Ptr'.
[all …]
/linux-6.3-rc2/Documentation/userspace-api/media/v4l/
A Dpixfmt-reserved.rst50 - 8 bit RGB format used by the BTTV driver.
55 - YUV format used by the gspca cpia1 driver.
66 - YUYV per line used by the gspca driver.
71 - YYUV per line used by the gspca driver.
76 - YUVY per line used by the gspca driver.
101 - OV511 JPEG format used by the gspca driver.
106 - OV518 JPEG format used by the gspca driver.
126 - Compressed format used by the Zoran driver
161 - Used by the Winnov Videum driver,
167 - Used by Trident tm6000
[all …]
/linux-6.3-rc2/arch/m68k/fpsp040/
A Dbinstr.S16 | bit 63. The fraction is multiplied by 10 using a mul by 2
33 | will be collected by the carry.
51 | d2: upper 32-bits of fraction for mul by 8
52 | d3: lower 32-bits of fraction for mul by 8
53 | d4: upper 32-bits of fraction for mul by 2
54 | d5: lower 32-bits of fraction for mul by 2
90 asll #3,%d2 |shift d2 left by 3 places
92 asll #3,%d3 |shift d3 left by 3 places
97 asll #1,%d5 |mul d5 by 2
98 roxll #1,%d4 |mul d4 by 2
[all …]
/linux-6.3-rc2/Documentation/driver-api/media/
A Dmc-core.rst41 Allocation of the structure is handled by the media device driver, usually by
45 Drivers initialise media device instances by calling
59 Entities are represented by a struct media_entity
65 Drivers initialize entity pads by calling
70 and unregistered by calling
76 Interfaces are represented by a
84 and remove them by calling:
124 Drivers create pad to pad links by calling:
173 Drivers initiate a graph traversal by calling
205 touched by entity drivers. Access to the field must be protected by the
[all …]
/linux-6.3-rc2/drivers/staging/media/atomisp/
A Dnotes.txt9 Memory is allocated by the hmm code. hmm_alloc() returns an ISP virtual
11 the hmm code finds the backing hmm-buffer-object (hmm_bo) by looking
14 The actual processing pipeline is made by loading one or more programs,
16 different binaries. Binaries are picked by filling a ia_css_binary_descr
24 (it is enabled by default) only the preview binary is loaded.
35 a camera_mipi_info struct. This struct is allocated/managed by
37 are filled by the atomisp core itself, like e.g. the port number.
39 Other members of camera_mipi_info which are set by some drivers are:
40 -metadata_width, metadata_height, metadata_effective_width, set by
41 the ov5693 driver (and used by the atomisp core)
[all …]
/linux-6.3-rc2/drivers/char/mwave/
A DREADME5 are not saved by the BIOS and so do not persist after unload and reload.
18 If the dsp irq has not been setup and stored in bios by the
20 irq used by the dsp to be configured.
23 If the dsp io range has not been setup and stored in bios by the
25 io range used by the dsp to be configured.
28 If the mwave's uart irq has not been setup and stored in bios by the
30 irq used by the mwave uart to be configured.
33 If the uart io range has not been setup and stored in bios by the
35 io range used by the mwave uart to be configured.
/linux-6.3-rc2/Documentation/sound/soc/
A Djack.rst11 to be present on a single jack but handled by separate bits of
18 This is done by splitting the jacks up into three things working
19 together: the jack itself represented by a struct snd_soc_jack, sets of
33 user space. The jack itself is completely passive, it is set up by the
34 machine driver and updated by jack detection methods.
36 Jacks are created by the machine driver calling snd_soc_jack_new().
52 Actual jack detection is done by code which is able to monitor some
53 input to the system and update a jack by calling snd_soc_jack_report(),
55 be set up by the machine driver, taking configuration for the jack to
59 provided by the snd_soc_jack_add_gpio() function. Other methods are
[all …]
/linux-6.3-rc2/Documentation/admin-guide/pm/
A Dintel_pstate.rst393 by this one.]
539 by scaling governors (in the `passive mode <Passive Mode_>`_) and by the driver
579 [Note that tasks may by migrated from one CPU to another by the scheduler's
594 returned by them).
596 The information returned by the ACPI ``_PSS`` objects is used by the
606 convention, the frequency returned by ``_PSS`` for that item is greater by 1 MHz
612 The list of P-states returned by ``_PSS`` is reflected by the table of
617 frequency reported by ``acpi-cpufreq`` is higher by 1 MHz than the frequency
640 the list returned by it.
656 processor is supported by it.
[all …]
/linux-6.3-rc2/Documentation/mhi/
A Dmhi.rst12 MHI is a protocol developed by Qualcomm Innovation Center, Inc. It is used
13 by the host processors to control and communicate with modem devices over high
29 which are mapped to the host memory space by the peripheral buses like PCIe.
34 MHI BHI registers: BHI (Boot Host Interface) registers are used by the host
37 Channel Doorbell array: Channel Doorbell (DB) registers used by the host to
50 All data structures used by MHI are in the host system memory. Using the
58 Transfer rings: Used by the host to schedule work items for a channel. The
90 Transfers between the host and device are organized by channels and defined by
108 * RP indicates the next element to be serviced by the device.
137 pointed by RP, increments the RP to the next element and triggers the
[all …]
/linux-6.3-rc2/drivers/staging/greybus/Documentation/firmware/
A Dfirmware-management10 All firmware packages on the Modules or Interfaces are managed by a special
11 Firmware Management Protocol. To support Firmware Management by the AP, the
61 be used by the user to identify the right character device for it. The class
144 fw_mgmt_ioc_get_fw' are filled by the kernel.
148 This ioctl shall be used by the user to get the version of a currently
151 in this case. The 'major' and 'minor' fields are set by the kernel in
159 'major' and 'minor' fields are set by the kernel in response.
166 set by the kernel in response.
176 This ioctl shall be used by the user to mode-switch the module to the
285 filled by the kernel.
[all …]
/linux-6.3-rc2/Documentation/virt/kvm/s390/
A Ds390-diag.rst18 DIAGNOSE calls by the guest cause a mandatory intercept. This implies
19 all supported DIAGNOSE calls need to be handled by either KVM or its
22 All DIAGNOSE calls supported by KVM use the RS-a format::
33 The supported DIAGNOSE function codes vary by the userspace used. For
53 Handled by userspace.
56 Handled by userspace.
59 Handled by userspace.
62 Handled by either userspace or KVM (ioeventfd case).
84 This function code is handled by userspace.
95 DIAGNOSE with function code 0x9c may improve system performance by
[all …]
/linux-6.3-rc2/Documentation/devicetree/bindings/power/
A Dpower-domain.yaml16 used for power gating of selected IP blocks for power saving by reduced leakage
20 their PM domains provided by PM domain providers. A PM domain provider can be
21 represented by any node in the device tree and can provide one or more PM
22 domains. A consumer node can refer to the provider by a phandle and a set of
49 the power domains provided by the provider have identical OPP tables,
58 by device tree binding documentation of particular provider.
62 A phandle and PM domain specifier as defined by bindings of the power
63 controller specified by phandle. Some power domains might be powered
67 by the given provider should be subdomains of the domain specified
68 by this binding.
[all …]
/linux-6.3-rc2/Documentation/pcmcia/
A Dlocking.rst62 protected by pcmcia_socket_list_rwsem;
67 The resource_ops and their data are protected by ops_mutex.
72 - by pcmcia_socket_list_rwsem::
76 - by thread_lock::
80 - by skt_mutex::
87 - by ops_mutex::
116 - by pcmcia_socket->ops_mutex::
128 - by the PCMCIA driver::
/linux-6.3-rc2/Documentation/ABI/testing/
A Dsysfs-secvar12 by the firmware.
21 On powernv/OPAL, this value is provided by the OPAL firmware
24 On pseries/PLPKS, this is generated by the kernel based on the
34 representation. The data and size can be determined by reading
60 defined by the secure variable implementation. All data is in
71 Currently only provided by PLPKS on the pseries platform.
84 Currently only provided by PLPKS on the pseries platform.
92 Currently only provided by PLPKS on the pseries platform.
100 Currently only provided by PLPKS on the pseries platform.
109 Currently only provided by PLPKS on the pseries platform.
[all …]
/linux-6.3-rc2/Documentation/livepatch/
A Dsystem-state.rst17 done by the already installed livepatches.
32 or by the newly used code. Also it must be possible to find changes done by
35 Each modified state is described by struct klp_state, see
51 is supported by the given livepatch.
90 has not been already modified by a livepatches that are being
94 been done by a livepatch that is being replaced.
100 done by livepatches that were being replaced.
116 are already provided by previously installed livepatches.
118 - Do any other preparatory action that is needed by
126 code or by calling *post_unpatch()* explicitly.
[all …]
/linux-6.3-rc2/drivers/media/v4l2-core/
A DKconfig18 This API is mostly used by camera interfaces in embedded platforms.
35 # Used by drivers that need tuner.ko
39 # Used by drivers that need v4l2-jpeg.ko
43 # Used by drivers that need v4l2-h264.ko
47 # Used by drivers that need v4l2-vp9.ko
51 # Used by drivers that need v4l2-mem2mem.ko
56 # Used by LED subsystem flash drivers
77 # Used by drivers that need Videobuf modules

Completed in 29 milliseconds

12345678910>>...136