vgaarb: Use dev_printk() when possible
authorBjorn Helgaas <bhelgaas@google.com>
Thu, 17 Nov 2016 17:47:58 +0000 (11:47 -0600)
committerDaniel Vetter <daniel.vetter@ffwll.ch>
Fri, 18 Nov 2016 09:43:20 +0000 (10:43 +0100)
commita75d68f62106fe66c4b8b96c0ee7155bdafc6f06
treed9acee2f9f7d967983abd93c86b7171f58c43a61
parent069cad6d02fef7924fb942b37a6c17dd02a79f7f
vgaarb: Use dev_printk() when possible

Use dev_printk() when possible.  This makes messages more consistent with
other device-related messages and, in some cases, adds useful information.
This changes messages like this:

  vgaarb: failed to allocate pci device
  vgaarb: setting as boot device: PCI:0000:01:00.0
  vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
  vgaarb: bridge control possible 0000:01:00.0

to this:

  pci 0000:01:00.0: vgaarb: failed to allocate VGA arbiter data
  pci 0000:01:00.0: vgaarb: setting as boot VGA device
  pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
  pci 0000:01:00.0: vgaarb: bridge control possible

No functional change intended.

Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: http://patchwork.freedesktop.org/patch/msgid/20161117174758.16810.67625.stgit@bhelgaas-glaptop.roam.corp.google.com
drivers/gpu/vga/vgaarb.c