Home
last modified time | relevance | path

Searched full:cc (Results 1 – 25 of 228) sorted by relevance

12345678910

/Documentation/devicetree/bindings/reset/
Dqcom,aoss-reset.yaml13 The bindings describe the reset-controller found on AOSS-CC (always on
21 - const: qcom,sc7180-aoss-cc
22 - const: qcom,sdm845-aoss-cc
26 - const: qcom,sc7280-aoss-cc
27 - const: qcom,sdm845-aoss-cc
31 - const: qcom,sdm845-aoss-cc
49 compatible = "qcom,sdm845-aoss-cc";
/Documentation/devicetree/bindings/clock/
Dqcom,krait-cc.txt9 "qcom,krait-cc-v1"
10 "qcom,krait-cc-v2"
30 compatible = "qcom,krait-cc-v1";
Dqcom,sdm845-lpasscc.yaml29 - const: cc
45 reg-names = "cc", "qdsp6ss";
Dqcom,sc7180-lpasscorecc.yaml46 - description: lpass core cc register
47 - description: lpass audio cc register
/Documentation/process/
Dstable-kernel-rules.rst73 Cc: stable@vger.kernel.org
75 Use ``Cc: stable@kernel.org`` instead when fixing unpublished vulnerabilities:
87 Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
88 Cc: <stable@vger.kernel.org> # 3.3.x: 1b9508f: sched: Rate-limit newidle
89 Cc: <stable@vger.kernel.org> # 3.3.x: fd21073: sched: Fix affinity logic
90 Cc: <stable@vger.kernel.org> # 3.3.x
113 Cc: <stable@vger.kernel.org> # 3.3.x
126 Cc: <stable@vger.kernel.org> # after -rc3
130 Cc: <stable@vger.kernel.org> # see patch description, needs adjustments for <= 6.3
136 Cc: <stable+noautosel@kernel.org> # reason goes here, and must be present
[all …]
Dsecurity-bugs.rst91 sense to Cc: both lists at once, except maybe for coordination if and
93 fix is accepted do not Cc: "linux-distros", and after it's merged do not
94 Cc: the kernel security team.
/Documentation/translations/it_IT/process/
Dstable-kernel-rules.rst83 Cc: stable@vger.kernel.org
85 Invece, usate ``Cc: stable@vger.kernel.org`` quando state inviando correzioni
100 Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
101 Cc: <stable@vger.kernel.org> # 3.3.x: 1b9508f: sched: Rate-limit newidle
102 Cc: <stable@vger.kernel.org> # 3.3.x: fd21073: sched: Fix affinity logic
103 Cc: <stable@vger.kernel.org> # 3.3.x
124 Cc: <stable@vger.kernel.org> # 3.3.x
136 Cc: <stable@vger.kernel.org> # after -rc3
140 Cc: <stable@vger.kernel.org> # see patch description, needs adjustments for <= 6.3
145 Cc: <stable+noautosel@kernel.org> # reason goes here, and must be present
[all …]
/Documentation/devicetree/bindings/extcon/
Dextcon-ptn5150.yaml7 title: PTN5150 CC (Configuration Channel) Logic device
13 PTN5150 is a small thin low power CC logic chip supporting the USB Type-C
14 connector application with CC control logic detection and indication
Dextcon-usbc-tusb320.yaml7 title: TI TUSB320 USB Type-C CC Logic controller
/Documentation/locking/
Dpreempt-locking.rst102 cpucache_t *cc; /* this is per-CPU */
104 cc = cc_data(searchp);
105 if (cc && cc->avail) {
106 __free_block(searchp, cc_entry(cc), cc->avail);
107 cc->avail = 0;
/Documentation/ABI/testing/
Ddebugfs-olpc10 To execute a command, write data with the format: CC:N A A A A
11 CC is the (hex) command, N is the count of expected reply bytes, and A A A A
Dsysfs-platform-sst-atom14 "v01.aa.bb.cc"
26 cc: Build version
/Documentation/kbuild/
Dmakefiles.rst319 are assigned. They are used for all the normal cc, as and ld
325 ccflags-y specifies options for compiling with $(CC).
374 $(CFLAGS_$@) specifies per-file options for $(CC). The $@
409 Thus, if you change an option to $(CC) all affected files will
535 $(CC) support functions
539 $(CC), each supporting a unique set of features and options.
540 kbuild provides basic support to check for valid options for $(CC).
541 $(CC) is usually the gcc compiler, but other alternatives are
545 as-option is used to check if $(CC) -- when used to compile
555 -Wa$(comma)-isa=$(isa-y) if it is supported by $(CC).
[all …]
Dkconfig-macro-language.rst18 CC := gcc
21 $(CC) -o $(APP) $(SRC)
35 CC := gcc
38 def_bool $(shell, $(srctree)/scripts/gcc-check-foo.sh $(CC))
57 a syntax error. The curly brace form as in ${CC} is not supported either.
/Documentation/admin-guide/
Dbug-bisect.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
129 want to contribute changes to the text -- but for copyright reasons please CC
134 This text is available under GPL-2.0+ or CC-BY-4.0, as stated at the top
135 of the file. If you want to distribute this text under CC-BY-4.0 only,
142 is available under CC-BY-4.0, as versions of this text that were processed
/Documentation/devicetree/bindings/usb/
Dqcom,pmic-typec.yaml45 - description: Type-C CC attach notification, VBUS error, tCCDebounce done
47 - description: Type-C CC state change
67 - const: cc-state-change
162 "cc-state-change",
/Documentation/devicetree/bindings/arm/
Damlogic.yaml91 - libretech,aml-s905x-cc
92 - libretech,aml-s905x-cc-v2
159 - libretech,aml-a311d-cc
204 - libretech,aml-s905d3-cc
/Documentation/devicetree/bindings/dma/
Dti-edma.txt3 The eDMA3 consists of two components: Channel controller (CC) and Transfer
4 Controller(s) (TC). The CC is the main entry for DMA users since it is
20 - reg: Memory map of eDMA CC
30 - ti,hwmods: Name of the hwmods associated to the eDMA CC.
225 - dma-channels: Specify total DMA channels per CC
/Documentation/devicetree/bindings/hwmon/
Dkontron,sl28cpld-hwmon.yaml10 - Michael Walle <michael@walle.cc>
/Documentation/RCU/Design/Expedited-Grace-Periods/
DExpRCUFlow.svg10 xmlns:cc="http://creativecommons.org/ns#"
26 <cc:Work
32 </cc:Work>
430 sodipodi:nodetypes="cc" />
436 sodipodi:nodetypes="cc" />
501 sodipodi:nodetypes="cc" />
554 sodipodi:nodetypes="cc" />
584 sodipodi:nodetypes="cc" />
590 sodipodi:nodetypes="cc" />
639 sodipodi:nodetypes="cc" />
[all …]
DExpSchedFlow.svg10 xmlns:cc="http://creativecommons.org/ns#"
26 <cc:Work
32 </cc:Work>
444 sodipodi:nodetypes="cc" />
450 sodipodi:nodetypes="cc" />
515 sodipodi:nodetypes="cc" />
556 sodipodi:nodetypes="cc" />
586 sodipodi:nodetypes="cc" />
592 sodipodi:nodetypes="cc" />
641 sodipodi:nodetypes="cc" />
[all …]
/Documentation/translations/ja_JP/
DSubmittingPatches190 必要としないパッチは Linus へ電子メールを送るか CC しなければなりません。
195 6) CC (カーボンコピー)先の選び方
197 特に理由がないなら、LKML にも CC してください。
218 加えたときには、いつもメンテナに CC するのを忘れないようにしてください。
382 13) いつ Acked-by: と Cc: を使うのか
407 その人を指す「Cc:」タグを任意で追加してもかまいません。これは指定された人からの
/Documentation/devicetree/bindings/pwm/
Dkontron,sl28cpld-pwm.yaml10 - Michael Walle <michael@walle.cc>
/Documentation/devicetree/bindings/watchdog/
Dkontron,sl28cpld-wdt.yaml10 - Michael Walle <michael@walle.cc>
/Documentation/gpu/rfc/
Dindex.rst10 considerations. Especially for uapi make sure you Cc: all relevant project

12345678910