lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAErSpo4dzRbVVN40x-1PFmCDMAB81=75r+kAuoDgDGXZHtQRQw@mail.gmail.com>
Date:   Thu, 28 Mar 2019 15:40:05 -0500
From:   Bjorn Helgaas <bhelgaas@...gle.com>
To:     Auger Eric <eric.auger@...hat.com>
Cc:     Bjorn Helgaas <helgaas@...nel.org>,
        Alex Williamson <alex.williamson@...hat.com>,
        kvm@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] vfio: Use dev_printk() when possible

On Mon, Mar 25, 2019 at 5:00 PM Auger Eric <eric.auger@...hat.com> wrote:
>
> Hi Bjorn,
> On 3/25/19 8:42 PM, Bjorn Helgaas wrote:
> > From: Bjorn Helgaas <bhelgaas@...gle.com>

> > --- a/drivers/vfio/platform/reset/vfio_platform_amdxgbe.c
> > +++ b/drivers/vfio/platform/reset/vfio_platform_amdxgbe.c
> > @@ -89,7 +89,8 @@ static int vfio_platform_amdxgbe_reset(struct vfio_platform_device *vdev)
> >       } while ((pcs_value & MDIO_CTRL1_RESET) && --count);
> >
> >       if (pcs_value & MDIO_CTRL1_RESET)
> > -             pr_warn("%s XGBE PHY reset timeout\n", __func__);
> > +             dev_warn(&vdev->device, "%s XGBE PHY reset timeout\n",
> vdev->device

Indeed, thank you!

> > @@ -63,7 +63,7 @@ static int vfio_platform_acpi_probe(struct vfio_platform_device *vdev,
> >
> >       adev = ACPI_COMPANION(dev);
> >       if (!adev) {
> > -             pr_err("VFIO: ACPI companion device not found for %s\n",
> > +             dev_err(dev, "VFIO: ACPI companion device not found for %s\n",
> >                       vdev->name);
> nit: for VFIO platform devices vdev->name and dev_name(dev) are the
> same. But for amba devices they are different I think so it looks
> sensible to keep both names at the moment.

OK, I'll keep this hunk as-is.

Bjorn

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ