Lines Matching full:partner
36 * partner possibilities.
38 * Firmware does not provide notification of vty partner changes to this
39 * driver. This means that an HMC Super Admin may add or remove partner vtys
40 * from a vty-server's partner list but the changes will not be signaled to
44 * rescanning partner information upon a user's request.
133 * tty_device pointers when the number of vty-server & vty partner connections
143 * vty-server & vty partner connections.
202 /* Status of partner info rescan triggered via sysfs. */
242 * partner info.
284 uint32_t p_unit_address; /* partner unit address */
285 uint32_t p_partition_ID; /* partner partition ID */
398 " partner vty@%X:%d connection.\n", in hvcs_vterm_state_store()
462 printk(KERN_INFO "HVCS: rescanning partner info for all" in rescan_store()
680 " partner vty@%X:%d connection.\n", in hvcs_destruct_port()
770 * This will populate the hvcs_struct's partner info fields for the in hvcs_probe()
774 printk(KERN_ERR "HVCS: Failed to fetch partner" in hvcs_probe()
851 * Traverse the list and add the partner info that is found to the hvcs_struct
852 * struct entry. NOTE: At this time I know that partner info will return a
853 * single entry but in the future there may be multiple partner info entries per
856 * partner info then hvcsd->p_* will hold the last partner info data from the
858 * partner info fields in hvcs_struct with a list of hvcs_partner_info
878 printk(KERN_ERR "HVCS: Failed to fetch partner" in hvcs_get_pi()
883 /* nixes the values if the partner vty went away */ in hvcs_get_pi()
929 * NOTE: It is possible that the super admin removed a partner vty and then
930 * added a different vty as the new partner.
941 * there isn't any now. This driver isn't notified when a new partner in hvcs_partner_connect()
979 printk(KERN_INFO "HVCS: vty-server or partner" in hvcs_partner_connect()
1083 printk(KERN_WARNING "HVCS: partner connect failed.\n"); in hvcs_install()
1288 * connection terminated between the vty-server and partner vty during in hvcs_write()