Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • I ipipe
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • xenomai
  • ipipe
  • Repository

Switch branch/tag
  • ipipe
  • drivers
  • gpu
  • drm
  • virtio
  • virtgpu_fb.c
Find file BlameHistoryPermalink
  • Gerd Hoffmann's avatar
    drm/virtio: fix framebuffer sparse warning · 71d3f6ef
    Gerd Hoffmann authored Nov 28, 2016
    virtio uses normal ram as backing storage for the framebuffer, so we
    should assign the address to new screen_buffer (added by commit
    17a7b0b4
    
    ) instead of screen_base.
    Reported-by: default avatarMichael S. Tsirkin <mst@redhat.com>
    Signed-off-by: default avatarGerd Hoffmann <kraxel@redhat.com>
    71d3f6ef

Replace virtgpu_fb.c

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.

Imprint & Privacy Policy