| /openbmc/linux/drivers/net/team/ |
| H A D | team.c | 64 static int team_port_set_team_dev_addr(struct team *team, in team_port_set_team_dev_addr() argument
67 return __set_port_dev_addr(port->dev, team->dev->dev_addr); in team_port_set_team_dev_addr()
70 int team_modeop_port_enter(struct team *team, struct team_port *port) in team_modeop_port_enter() argument
72 return team_port_set_team_dev_addr(team, port); in team_modeop_port_enter()
76 void team_modeop_port_change_dev_addr(struct team *team, in team_modeop_port_change_dev_addr() argument
79 team_port_set_team_dev_addr(team, port); in team_modeop_port_change_dev_addr()
117 static struct team_option *__team_find_option(struct team *team, in __team_find_option() argument
122 list_for_each_entry(option, &team->option_list, list) { in __team_find_option()
135 static void __team_option_inst_del_option(struct team *team, in __team_option_inst_del_option() argument
140 list_for_each_entry_safe(opt_inst, tmp, &team->option_inst_list, list) { in __team_option_inst_del_option()
[all …]
|
| 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 | team_mode_loadbalance.c | 17 static rx_handler_result_t lb_receive(struct team *team, struct team_port *port, in lb_receive() argument
32 typedef struct team_port *lb_select_tx_port_func_t(struct team *,
58 struct team *team; member
75 static struct lb_priv *get_lb_priv(struct team *team) in get_lb_priv() argument
77 return (struct lb_priv *) &team->mode_priv; in get_lb_priv()
96 static void lb_tx_hash_to_port_mapping_null_port(struct team *team, in lb_tx_hash_to_port_mapping_null_port() argument
99 struct lb_priv *lb_priv = get_lb_priv(team); in lb_tx_hash_to_port_mapping_null_port()
114 team_options_change_check(team); in lb_tx_hash_to_port_mapping_null_port()
118 static struct team_port *lb_hash_select_tx_port(struct team *team, in lb_hash_select_tx_port() argument
121 int port_index = team_num_to_port_index(team, hash); in lb_hash_select_tx_port()
[all …]
|
| H A D | team_mode_roundrobin.c | 18 static struct rr_priv *rr_priv(struct team *team) in rr_priv() argument
20 return (struct rr_priv *) &team->mode_priv; in rr_priv()
23 static bool rr_transmit(struct team *team, struct sk_buff *skb) in rr_transmit() argument
28 port_index = team_num_to_port_index(team, in rr_transmit()
29 rr_priv(team)->sent_packets++); in rr_transmit()
30 port = team_get_port_by_index_rcu(team, port_index); in rr_transmit()
33 port = team_get_first_port_txable_rcu(team, port); in rr_transmit()
36 if (team_dev_queue_xmit(team, port, skb)) in rr_transmit()
|
| 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_random.c | 14 static bool rnd_transmit(struct team *team, struct sk_buff *skb) in rnd_transmit() argument
19 port_index = get_random_u32_below(team->en_port_count); in rnd_transmit()
20 port = team_get_port_by_index_rcu(team, port_index); in rnd_transmit()
23 port = team_get_first_port_txable_rcu(team, port); in rnd_transmit()
26 if (team_dev_queue_xmit(team, port, skb)) in rnd_transmit()
|
| 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()
|
| /openbmc/linux/include/linux/ |
| H A D | if_team.h | 26 struct team;
32 struct team *team; member
115 int (*init)(struct team *team);
116 void (*exit)(struct team *team);
117 rx_handler_result_t (*receive)(struct team *team,
120 bool (*transmit)(struct team *team, struct sk_buff *skb);
121 int (*port_enter)(struct team *team, struct team_port *port);
122 void (*port_leave)(struct team *team, struct team_port *port);
123 void (*port_change_dev_addr)(struct team *team, struct team_port *port);
124 void (*port_enabled)(struct team *team, struct team_port *port);
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libteam/ |
| H A D | libteam_1.32.bb | 1 SUMMARY = "Library for controlling team network device"
38 # Ensure kernel has these mods enabled features/net/team/team.scc
39 RRECOMMENDS:${PN} += "kernel-module-team kernel-module-team-mode-activebackup \
40 kernel-module-team-mode-broadcast \
41 kernel-module-team-mode-loadbalance \
42 kernel-module-team-mode-random \
43 kernel-module-team-mode-roundrobin"
|
| /openbmc/docs/security/ |
| H A D | obmc-security-response-team.md | 10 - a security response team to address reported vulnerabilities
11 - the openbmc-security email address for the response team
12 - guidelines for security response team members
16 1. A community member reports a problem privately to the security response team
18 2. The responders (including the security response team, the repository
27 Note that the OpenBMC security response team is distinct from the OpenBMC
38 security response team, and the initial communication between the security
39 response team members.
42 [Guidelines for security response team members](./obmc-security-response-team-guidelines.md)
43 contain collected wisdom for the response team and community members who are
|
| H A D | obmc-security-response-team-guidelines.md | 1 # Security response team guidelines
4 response team, project owners, and community members who are responding to
8 vulnerabilities. The security response team helps the maintainers, provides
47 response team. For example, link to these guidelines.
55 - Submit the problem to another security response team, for example, the
93 public) publish the security advisory, and email the security-response team.
95 [security vulnerability reporting process]: ./obmc-security-response-team.md
97 [uefi security response team (usrt)]: https://uefi.org/security
113 The OpenBMC security response team has received the problem.
150 The OpenBMC Security Response team has released an OpenBMC Security Advisory:
[all …]
|
| H A D | how-to-report-a-security-vulnerability.md | 14 To begin the process: Privately contact the OpenBMC security response team and
20 not, the security response team will help route the problem.
29 the security response team can help you route the problem.
37 - The OpenBMC security response team.
43 response team) will help clarify the problem and assign CVEs.
46 response team guidelines][].
70 [security response team guidelines]: ./obmc-security-response-team-guidelines.md
|
| H A D | obmc-github-security-advisory-template.md | 4 new draft GitHub security advisories as part of the [Security response team
10 [security response team guidelines]: ./obmc-security-response-team-guidelines.md
27 Please coordinate with the security response team
|
| /openbmc/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 | 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 The kernel security team strongly recommends that reporters of potential
71 AFTER discussing it with the kernel security team. Do not Cc: both
82 The security team does not assign CVEs, nor do we require them for
92 The Linux kernel security team is not a formal body and therefore unable
|
| /openbmc/qemu/docs/devel/ |
| H A D | trivial-patches.rst | 14 The trivial patches team take on the task of reviewing and building pull
27 Since the trivial patch team rotates maintainership there is only one
35 The trivial patches team rotates the duty of collecting trivial patches
36 amongst its members. A team member's job is to:
43 A single team member can be on duty as long as they like. The suggested
49 If you would like to join the trivial patches team, contact Laurent
50 Vivier. The current team includes:
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | security-subjects.rst | 14 the operation of the YP Security team and how to contribute in the
29 Yocto Project Security team.
67 vulnerabilities. The list is monitored by the Yocto Project Security team.
77 copy to the security team at the Yocto Project as well. If you believe this is
82 Security team
85 The Yocto Project/OpenEmbedded security team coordinates the work on security
90 Security team appointment
100 Technical Steering Committee (OE TSC) and the final list of the team members
113 for. They do not share information about confidential issues outside of the team
120 The YP security team organizes its meetings and communication as needed.
[all …]
|
| /openbmc/docs/designs/ |
| H A D | ci-authorization.md | 26 openbmc/general-developers GitHub team. If the contributor is a member of the
27 team (or a general-developers sub-team), the automated CI processes are
29 the general-developers team, manual intervention (ok-to-test) is required by a
39 openbmc/general-developers GitHub team, the contributor must first be a member
56 team, and all subordinate teams, to Gerrit groups:
87 Gerrit group instead of the GitHub team.
|
| /openbmc/openbmc/poky/meta/recipes-support/iso-codes/ |
| H A D | iso-codes_4.17.0.bb | 5 HOMEPAGE = "https://salsa.debian.org/iso-codes-team/iso-codes"
6 BUGTRACKER = "https://salsa.debian.org/iso-codes-team/iso-codes/issues"
11 SRC_URI = "git://salsa.debian.org/iso-codes-team/iso-codes.git;protocol=https;branch=main;"
|
| /openbmc/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.
|
| /openbmc/docs/ |
| H A D | SECURITY.md | 26 The OpenBMC security response team (SRT) will respond to you and work to address
31 response team guidelines][].
55 [security response team guidelines]: ./obmc-security-response-team-guidelines.md
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-keras-applications_1.0.8.bb | 2 HOMEPAGE = "https://github.com/keras-team/keras-applications"
7 SRC_URI = "git://github.com/keras-team/keras-applications.git;branch=master;protocol=https"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/consolation/ |
| H A D | consolation_0.0.9.bb | 6 HOMEPAGE = "https://salsa.debian.org/consolation-team/consolation"
17 SRC_URI = "git://salsa.debian.org/consolation-team/consolation.git;branch=master"
|
| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | concepts-appx.rst | 13 development cycle, the Yocto Project team chooses a Linux kernel based
20 team knows that the ``kernel.org`` final release will clearly be within
23 This balance allows the Yocto Project team to deliver the most
25 team has a stable official release for the baseline Linux kernel
95 Once a Yocto Linux kernel is officially released, the Yocto Project team
104 During the uprev cycle, the Yocto Project team uses an ongoing analysis
107 subsequent Yocto Linux kernel development. The team continually monitors
109 interest. The team does consider back-porting large features if they
117 team's Yocto Linux kernel development strategy. It is the Yocto Project
118 team's policy to not back-port minor features to the released Yocto
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/tiptop/ |
| H A D | tiptop_2.3.1.bb | 2 HOMEPAGE = "https://team.inria.fr/pacap/software/tiptop/"
15 UPSTREAM_CHECK_URI = "https://team.inria.fr/pacap/software/tiptop/"
|