Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • linux
  • Repository
  • linux
  • include
  • net
  • devlink.h
Find file BlameHistoryPermalink
  • Jiri Pirko's avatar
    devlink: bring port new reply back · 5ff9424e
    Jiri Pirko authored May 31, 2023
    In the offending fixes commit I mistakenly removed the reply message of
    the port new command. I was under impression it is a new port
    notification, partly due to the "notify" in the name of the helper
    function. Bring the code sending reply with new port message back, this
    time putting it directly to devlink_nl_cmd_port_new_doit()
    
    Fixes: c496daeb
    
     ("devlink: remove duplicate port notification")
    Signed-off-by: default avatarJiri Pirko <jiri@nvidia.com>
    Reviewed-by: default avatarSimon Horman <simon.horman@corigine.com>
    Link: https://lore.kernel.org/r/20230531142025.2605001-1-jiri@resnulli.us
    
    
    Signed-off-by: default avatarJakub Kicinski <kuba@kernel.org>
    5ff9424e
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7