[PATCH v2] vgaarb: Use dev_printk() when possible

2016-11-18 Thread Daniel Vetter
On Thu, Nov 17, 2016 at 02:20:59PM -0600, Bjorn Helgaas wrote: > On Thu, Nov 17, 2016 at 07:59:21PM +0100, Daniel Vetter wrote: > > On Thu, Nov 17, 2016 at 11:47:58AM -0600, Bjorn Helgaas wrote: > > > Use dev_printk() when possible. This makes messages more consistent with > > > other

[PATCH v2] vgaarb: Use dev_printk() when possible

2016-11-17 Thread Daniel Vetter
On Thu, Nov 17, 2016 at 11:47:58AM -0600, Bjorn Helgaas wrote: > 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 >

[PATCH v2] vgaarb: Use dev_printk() when possible

2016-11-17 Thread Bjorn Helgaas
On Thu, Nov 17, 2016 at 07:59:21PM +0100, Daniel Vetter wrote: > On Thu, Nov 17, 2016 at 11:47:58AM -0600, Bjorn Helgaas wrote: > > Use dev_printk() when possible. This makes messages more consistent with > > other device-related messages and, in some cases, adds useful information. > > This

[PATCH v2] vgaarb: Use dev_printk() when possible

2016-11-17 Thread Bjorn Helgaas
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::01:00.0 vgaarb: device added: