| /linux/drivers/net/team/ |
| H A D | team_mode_activebackup.c | 21 static struct ab_priv *ab_priv(struct team *team) in ab_priv() argument 23 return (struct ab_priv *) &team->mode_priv; in ab_priv() 26 static rx_handler_result_t ab_receive(struct team *team, struct team_port *port, in ab_receive() argument 30 active_port = rcu_dereference(ab_priv(team)->active_port); in ab_receive() 36 static bool ab_transmit(struct team *team, struct sk_buff *skb) in ab_transmit() argument 40 active_port = rcu_dereference_bh(ab_priv(team)->active_port); in ab_transmit() 43 if (team_dev_queue_xmit(team, active_port, skb)) in ab_transmit() 52 static void ab_port_leave(struct team *team, struct team_port *port) in ab_port_leave() argument 54 if (ab_priv(team)->active_port == port) { in ab_port_leave() 55 RCU_INIT_POINTER(ab_priv(team)->active_port, NULL); in ab_port_leave() [all …]
|
| H A D | Kconfig | 3 tristate "Ethernet team driver support" 11 "ip link add link [ address MAC ] [ NAME ] type team" 14 will be called team. 24 All added ports are setup to have team's device address. 26 To compile this team mode as a module, choose M here: the module 36 All added ports are setup to have team's device address. 38 To compile this team mode as a module, choose M here: the module 48 All added ports are setup to have team's device address. 50 To compile this team mode as a module, choose M here: the module 63 To compile this team mode as a module, choose M here: the module [all …]
|
| H A D | team_mode_broadcast.c | 14 static bool bc_transmit(struct team *team, struct sk_buff *skb) in bc_transmit() argument 22 list_for_each_entry_rcu(cur, &team->port_list, list) { in bc_transmit() 27 ret = !team_dev_queue_xmit(team, last, in bc_transmit() 37 ret = !team_dev_queue_xmit(team, last, skb); in bc_transmit()
|
| H A D | Makefile | 6 team-y:= team_core.o team_nl.o 7 obj-$(CONFIG_NET_TEAM) += team.o
|
| /linux/Documentation/process/ |
| H A 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 …]
|
| H A 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 …]
|
| H A D | security-bugs.rst | 50 "system freezes each time I run this command"), the security team will help 78 It turns out that the majority of the bugs reported via the security team are 93 team's experience shows that bugs discovered this way systematically surface 100 privately: the security team would rather triage a borderline report than miss 109 affected subsystem's maintainers and Cc: the Linux kernel security team. Do 166 the Linux kernel security team only. Your message will be triaged, and you 173 A significant fraction of bug reports submitted to the security team are 235 The security team and maintainers almost always require additional 239 patches). Before contacting the security team, the reporter must ensure 247 security team who will ensure the message is delivered to the proper [all …]
|
| H A 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.
|
| H A D | contribution-maturity-model.rst | 78 * The number of upstream kernel contributions by team or organization
|
| /linux/Documentation/admin-guide/cifs/ |
| H A D | authors.rst | 11 Andrew Tridgell (Samba team) for his early suggestions about SMB/CIFS VFS 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.
|
| /linux/tools/testing/selftests/net/ |
| H A D | rtnetlink.sh | 660 local team="test_team1" 664 run_cmd ip link add $team type team 671 run_cmd ip link set $dummy master $team 672 run_cmd ip link set $team up 675 run_cmd ip link set $team master $bridge 682 run_cmd ip link del $team 699 local team="test_team1" 702 run_cmd ip link add $team up type team 706 run_cmd ip link set $team master $bridge 716 run_cmd ip link del $team [all …]
|
| /linux/fs/smb/server/ |
| H A D | Kconfig | 35 https://github.com/cifsd-team/ksmbd-tools. 38 (https://github.com/cifsd-team/ksmbd-tools/blob/master/README).
|
| /linux/Documentation/networking/device_drivers/ethernet/wangxun/ |
| H A D | txgbe.rst | 19 If you got any problem, contact Wangxun support team via nic-support@net-swift.com
|
| H A D | ngbe.rst | 13 customer support team via email at nic-support@net-swift.com or check our website
|
| H A D | ngbevf.rst | 15 If you got any problem, contact Wangxun support team via nic-support@net-swift.com
|
| H A D | txgbevf.rst | 15 If you got any problem, contact Wangxun support team via nic-support@net-swift.com
|
| /linux/tools/testing/selftests/drivers/net/team/ |
| H A D | refleak.sh | 13 ip -n "$ns1" link add name team1 type team
|
| H A D | non_ether_header_ops.sh | 24 ip -n "$ns1" link add t0 type team
|
| /linux/Documentation/networking/ |
| H A D | index.rst | 122 team
|
| /linux/Documentation/translations/ja_JP/ |
| H A D | stable_kernel_rules.txt | 4 and JF Project team <www.linux.or.jp/JF>.
|
| H A D | stable_api_nonsense.txt | 4 and the JF Project team <http://www.linux.or.jp/JF/>.
|
| /linux/Documentation/translations/zh_CN/networking/ |
| H A D | index.rst | 139 * team
|
| /linux/Documentation/nvdimm/ |
| H A D | maintainer-entry-profile.rst | 39 be assigned a format-interface-code from the NVDIMM Sub-team of the ACPI
|
| /linux/Documentation/filesystems/smb/ |
| H A 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)
|
| /linux/tools/testing/selftests/ |
| H A D | Makefile | 26 TARGETS += drivers/net/team
|