Searched full:developed (Results 1 – 25 of 107) sorted by relevance
12345
| /Documentation/translations/zh_TW/process/ |
| D | submitting-patches.rst | 337 何時使用Acked-by:，Cc:，和Co-developed-by:
359 Co-developed-by: 聲明補丁是由多個開發人員共同創建的；當幾個人在一個補丁上工
360 作時，它用於給出共同作者（除了From:所給出的作者之外）。因爲Co-developed-by:
361 表示作者身份，所以每個Co-developed-by:必須緊跟在相關合作作者的簽署之後。標準
363 過From:還是Co-developed-by:表明。值得注意的是，最後一個Signed-off-by:必須是
372 Co-developed-by: First Co-Author <first@coauthor.example.org>
374 Co-developed-by: Second Co-Author <second@coauthor.example.org>
384 Co-developed-by: Random Co-Author <random@coauthor.example.org>
387 Co-developed-by: Submitting Co-Author <sub@coauthor.example.org>
|
| D | 5.Posting.rst | 171 - Co-developed-by: 聲明補丁是由多個開發人員共同創建的；當幾個人在一個補丁上
173 Co-developed-by: 表示作者身份，所以每個共同開發人，必須緊跟在相關合作作者
|
| /Documentation/translations/zh_CN/process/ |
| D | submitting-patches.rst | 336 何时使用Acked-by:，Cc:，和Co-developed-by:
358 Co-developed-by: 声明补丁是由多个开发人员共同创建的；当几个人在一个补丁上工
359 作时，它用于给出共同作者（除了From:所给出的作者之外）。因为Co-developed-by:
360 表示作者身份，所以每个Co-developed-by:必须紧跟在相关合作作者的签署之后。标准
362 过From:还是Co-developed-by:表明。值得注意的是，最后一个Signed-off-by:必须是
371 Co-developed-by: First Co-Author <first@coauthor.example.org>
373 Co-developed-by: Second Co-Author <second@coauthor.example.org>
383 Co-developed-by: Random Co-Author <random@coauthor.example.org>
386 Co-developed-by: Submitting Co-Author <sub@coauthor.example.org>
|
| D | 5.Posting.rst | 168 - Co-developed-by: 声明补丁是由多个开发人员共同创建的；当几个人在一个补丁上
170 Co-developed-by: 表示作者身份，所以每个共同开发人，必须紧跟在相关合作作者
|
| /Documentation/security/ |
| D | lsm.rst | 21 projects (e.g. RSBAC, Medusa) have also developed flexible access
23 developed particular access control models for Linux (e.g. LIDS, DTE,
24 SubDomain). Each project has developed and maintained its own kernel
|
| /Documentation/devicetree/bindings/firmware/ |
| D | mediatek,geniezone.yaml | 13 GenieZone is a proprietary type-I hypervisor firmware developed by MediaTek,
|
| /Documentation/filesystems/ |
| D | btrfs.rst | 9 Jointly developed by several companies, licensed under the GPL and open for
|
| /Documentation/driver-api/memory-devices/ |
| D | ti-gpmc.rst | 29 generic timing routine was developed to achieve above requirements.
48 A word of caution: generic timing routine has been developed based
|
| /Documentation/devicetree/bindings/counter/ |
| D | interrupt-counter.yaml | 13 A generic interrupt counter to measure interrupt frequency. It was developed
|
| /Documentation/devicetree/bindings/iommu/ |
| D | pkvm,pviommu.yaml | 15 pvIOMMU was initially developed for protected KVM (pKVM), but it has no
|
| /Documentation/networking/ |
| D | sctp.rst | 14 developed the SCTP protocol and later handed the protocol over to the
|
| D | 6pack.rst | 47 2. Who has developed the 6pack protocol?
50 The 6pack protocol has been developed by Ekki Plicht DF4OR, Henning Rech
|
| /Documentation/accounting/ |
| D | cgroupstats.rst | 26 has been developed, the sample output of the utility is shown below::
|
| /Documentation/devicetree/bindings/net/can/ |
| D | ctu,ctucanfd.yaml | 10 Open-source CAN FD IP core developed at the Czech Technical University in Prague
|
| /Documentation/translations/it_IT/process/ |
| D | submitting-patches.rst | 499 Quando utilizzare Acked-by:, Cc:, e Co-developed-by:
532 Co-developed-by: indica che la patch è stata cosviluppata da diversi
535 che Co-developed-by: implica la paternità della patch, ogni Co-developed-by:
540 la paternità venga assegnata via From: o Co-developed-by:. Da notare che
551 Co-developed-by: First Co-Author <first@coauthor.example.org>
553 Co-developed-by: Second Co-Author <second@coauthor.example.org>
557 Esempio di una patch sottomessa dall'autore Co-developed-by:::
563 Co-developed-by: Random Co-Author <random@coauthor.example.org>
566 Co-developed-by: Submitting Co-Author <sub@coauthor.example.org>
|
| /Documentation/translations/sp_SP/process/ |
| D | submitting-patches.rst | 488 Cuándo usar Acked-by:, Cc: y Co-developed-by por:
523 Co-developed-by: establece que el parche fue co-creado por múltiples
526 un solo parche. Ya que Co-developed-by: denota autoría, cada
527 Co-developed-by: debe ser inmediatamente seguido de Signed-off-by: del
531 atribuye a través de From: o Co-developed-by:. Cabe destacar que el último
542 Co-developed-by: Primer coautor <primer@coauthor.example.org>
544 Co-developed-by: Segundo coautor <segundo@coautor.ejemplo.org>
548 Ejemplo de un parche enviado por un Co-developed-by: autor::
554 Co-developed-by: Co-Autor aleatorio <aleatorio@coauthor.example.org>
557 Co-developed-by: Coautor que envió <sub@coauthor.example.org>
|
| /Documentation/process/ |
| D | submitting-patches.rst | 456 When to use Acked-by:, Cc:, and Co-developed-by:
489 Co-developed-by: states that the patch was co-created by multiple developers;
492 Co-developed-by: denotes authorship, every Co-developed-by: must be immediately
496 the author is attributed via From: or Co-developed-by:. Notably, the last
506 Co-developed-by: First Co-Author <first@coauthor.example.org>
508 Co-developed-by: Second Co-Author <second@coauthor.example.org>
512 Example of a patch submitted by a Co-developed-by: author::
518 Co-developed-by: Random Co-Author <random@coauthor.example.org>
521 Co-developed-by: Submitting Co-Author <sub@coauthor.example.org>
|
| D | 8.Conclusion.rst | 57 Linux kernel is developed and how you can participate in that process.
|
| /Documentation/arch/riscv/ |
| D | patch-acceptance.rst | 8 The RISC-V instruction set architecture is developed in the open:
|
| /Documentation/i2c/busses/ |
| D | i2c-sis96x.rst | 23 named chipset combinations. The driver was developed without benefit of a
|
| /Documentation/input/devices/ |
| D | bcm5974.rst | 64 The driver was developed at the ubuntu forums in June 2008 [#f1]_, and now has
|
| /Documentation/mm/ |
| D | page_tables.rst | 11 included in the Intel 80386, which was the CPU Linux 1.0 was developed on.
38 Over time a deeper hierarchy has been developed in response to increasing memory
61 The page table hierarchy has now developed into this::
|
| /Documentation/arch/arm/ |
| D | marvell.rst | 368 * This line of SoCs originates from the XScale family developed by
370 PXA26x, PXA27x, PXA3xx and PXA93x were developed by Intel, while
371 the later PXA95x were developed by Marvell.
422 * This line of SoCs originates from the XScale family developed by
424 this MMP/MMP2 family were developed by Marvell.
472 PXA processors. Feroceon is a Marvell designed core that developed in-house,
|
| /Documentation/watchdog/ |
| D | hpwdt.rst | 76 The HPE iLO NMI Watchdog Driver and documentation were originally developed
|
| /Documentation/i2c/ |
| D | summary.rst | 6 a protocol developed by Philips. It is a two-wire protocol with variable
|
12345