Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L linux-vm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • linux-arm
  • linux-vm
  • Repository
  • linux-vm
  • drivers
  • net
  • dsa
  • mv88e6xxx.c
Find file BlameHistoryPermalink
  • Vivien Didelot's avatar
    net: dsa: mv88e6xxx: write VID outside of VTU Get Next code · 36d04ba1
    Vivien Didelot authored Oct 22, 2015
    
    
    There is no need to write the VLAN ID before every Get Next operation,
    since the VTU VID register is not cleared between calls.
    
    Move the VID write call in a _mv88e6xxx_vtu_vid_write function outside
    of _mv88e6xxx_vtu_getnext so future code could call VTU Get Next
    multiple times and save a few register accesses.
    
    Signed-off-by: default avatarVivien Didelot <vivien.didelot@savoirfairelinux.com>
    Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    36d04ba1