Searched full:team (Results 1 – 25 of 50) sorted by relevance
12
| /Documentation/netlink/specs/ |
| D | team.yaml | 3 name: team
8 Network team device driver.
10 c-family-name: team-genl-name
11 c-version-name: team-genl-version
27 name: team
29 The team nested layout of get/set msg looks like
42 name-prefix: team-attr-
49 name: team-ifindex
61 name-prefix: team-attr-item-
63 attr-max-name: team-attr-item-option-max
[all …]
|
| /Documentation/process/ |
| D | embargoed-hardware-issues.rst | 25 The Linux kernel hardware security team is separate from the regular Linux
26 kernel security team.
28 The team only handles developing fixes for embargoed hardware security
30 handled by this team and the reporter will be guided to contact the regular
31 Linux kernel security team (:ref:`Documentation/admin-guide/
34 The team can be contacted by email at <hardware-security@kernel.org>. This
53 The current team of hardware security officers:
77 The Linux kernel hardware security team is not a formal body and therefore
94 The Linux kernel community has a dedicated hardware security team for
98 The hardware security team identifies the developers (domain experts) who
[all …]
|
| D | security-bugs.rst | 9 Linux kernel security team.
14 The Linux kernel security team can be contacted by email at
19 security team will bring in extra help from area maintainers to
69 While the kernel security team solely focuses on getting bugs fixed,
79 security team and other teams is difficult since for the kernel security
80 team occasional embargoes (as subject to a maximum allowed number of
85 As such, the kernel security team strongly recommends that as a reporter
94 Cc: the kernel security team.
99 The security team does not assign CVEs, nor do we require them for
103 assignment team<../process/cve>` to obtain one.
[all …]
|
| D | cve.rst | 16 The Linux kernel developer team does have the ability to assign CVEs for
39 fixed. Because of this, the CVE assignment team is overly cautious and
42 kernel team.
44 If the CVE assignment team misses a specific fix that any user feels
46 and the team there will work with you on it. Note that no potential
58 contact the kernel CVE assignment team at <cve@kernel.org> to get an
63 team. A list of the currently supported kernel branches can be found at
86 can not be assigned by the Linux kernel CVE team, and must be asked for
91 CVE team should not be treated as a valid CVE. Please notify the
92 kernel CVE assignment team at <cve@kernel.org> so that they can work to
[all …]
|
| D | stable-kernel-rules.rst | 47 2. Ask the stable team to pick up a patch already mainlined.
48 3. Submit a patch to the stable team that is equivalent to a change already
82 To send additional instructions to the stable team, use a shell-style inline
121 Note, such tagging is unnecessary if the stable team can derive the
133 team's backporting tools (e.g AUTOSEL or scripts that look for commits
174 days, according to the schedules of the stable team members.
203 security kernel team, and not go through the normal review cycle.
204 Contact the kernel security team for more details on this procedure.
|
| D | contribution-maturity-model.rst | 78 * The number of upstream kernel contributions by team or organization
|
| D | kernel-docs.rst | 184 :Author: The Linux-MM team.
|
| /Documentation/admin-guide/cifs/ |
| D | authors.rst | 11 Andrew Tridgell (Samba team) for his early suggestions about SMB/CIFS VFS
13 this project, to Jim McDonough from IBM (and the Samba Team) for his help, to
14 the IBM Linux JFS team for explaining many esoteric Linux filesystem features.
15 Jeremy Allison of the Samba team has done invaluable work in adding the server
24 thanks to the Samba team for their technical advice and encouragement.
42 - Kazeon team for various fixes especially for 2.4 version.
|
| /Documentation/networking/ |
| D | team.rst | 4 Team title
7 Team devices are driven from userspace via libteam library which is here:
|
| D | index.rst | 121 team
|
| /Documentation/networking/device_drivers/ethernet/wangxun/ |
| D | ngbe.rst | 13 customer support team via email at nic-support@net-swift.com or check our website
|
| D | txgbe.rst | 19 If you got any problem, contact Wangxun support team via nic-support@net-swift.com
|
| /Documentation/gpu/amdgpu/display/ |
| D | index.rst | 35 * Prepare a branch with those patches for our validation team. If there is an
70 Notice that someone from our test team will always reply to the cover letter
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | fsl,intmux.yaml | 11 - NXP Linux Team <linux-imx@nxp.com>
|
| /Documentation/translations/ja_JP/ |
| D | stable_kernel_rules.txt | 4 and JF Project team <www.linux.or.jp/JF>.
|
| D | SubmitChecklist | 4 and the JF Project team <http://www.linux.or.jp/JF/>.
|
| D | stable_api_nonsense.txt | 4 and the JF Project team <http://www.linux.or.jp/JF/>.
|
| /Documentation/devicetree/bindings/net/ |
| D | nxp,dwmac-imx.yaml | 12 - NXP Linux Team <linux-imx@nxp.com>
|
| D | fsl,fec.yaml | 12 - NXP Linux Team <linux-imx@nxp.com>
|
| /Documentation/nvdimm/ |
| D | maintainer-entry-profile.rst | 39 be assigned a format-interface-code from the NVDIMM Sub-team of the ACPI
|
| /Documentation/devicetree/bindings/display/imx/ |
| D | fsl,imx-lcdc.yaml | 11 - Pengutronix Kernel Team <kernel@pengutronix.de>
|
| /Documentation/filesystems/smb/ |
| D | ksmbd.rst | 124 1. Download ksmbd-tools(https://github.com/cifsd-team/ksmbd-tools/releases) and
127 - Refer to README(https://github.com/cifsd-team/ksmbd-tools/blob/master/README.md)
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | panel-simple.yaml | 277 # Team Source Display Technology TST043015CMHX 4.3" WQVGA TFT LCD panel
278 - team-source-display,tst043015cmhx
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-mellanox-bootctl | 135 This value is provided by the manufacturing team.
|
| /Documentation/translations/sp_SP/process/ |
| D | kernel-docs.rst | 145 :Autor: The Linux-MM team.
|
12