Received: by 2002:a25:5b86:0:0:0:0:0 with SMTP id p128csp1727107ybb; Fri, 29 Mar 2019 10:04:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqyNdsZJ/AecDPyvomUfnDO3/OW1zpKT2ne2aU/TeY+v1ZTS3AKHfIMMFQQlCv86O3KYt358 X-Received: by 2002:a17:902:aa5:: with SMTP id 34mr47974137plp.302.1553879056603; Fri, 29 Mar 2019 10:04:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553879056; cv=none; d=google.com; s=arc-20160816; b=p5/S2MSqMg2wKXO0s5Gd5zU6Bla9ak7eStJV4LbfuVQjVo2bC4AtFNu68XRf6KkKGr c+qxHe0wwUXWJxlnMFmmZe4m/pnmVk/oLeEq8BhTRkwlZ3sgnGdWrBi164JCGppVNt7s W8o7mHuoo5fNiUQsrLdaV+FY4WhEC12ldHCpkkUuNUPH8giLhitLfzCSkjZy43VfvzAy SEZ3nlGs9odUYjWVuaG2ZD6MOrMReJmNcfg/RVRwNCE+tegcb98oFvDIHTxUS7upM9oM /bN+PIwkcvRoYme3qK0TPGvtXWqbhmbXzya1tPJ64NimZaWLLpe2eazzmUibr29f29NA 1GBQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=4h7VtKuChw0e0QSGqGDCThC9qDFXbr94ocjisp/vP48=; b=w5bkiXhD03u0y3JemkizQxd5DhXqUUCgXynbdDSq8MOhaJakn1tQD7GoMGXr6UKYas qExWemjlS5RsXkf7w8q4IihQUYDyNoCVKZbaG6FfPKZk64edTPnNn1GYblZSDt4YYewG d3vcm/BAb/gu2KVzcnZtUW4wPVCPJMviMYqtcAJU2ko4EKTT5s6lyPiNkvU1CAN8EtRz 7N6+WVlOpoJSnYdYN0YV7iQhr72KhmrSKZmgLWBg6UgujBKwUl8jB9Lq//7KOsEqgcGm KQwEwS4n35JqSK0Ur79NXUYUcDzg5LMTZ0EaBVX+ziMH49Jcprqc3mWjzdc9gfR40MCp vYHw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=DK5NTXZp; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o9si2231050pgv.25.2019.03.29.10.03.59; Fri, 29 Mar 2019 10:04:16 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=DK5NTXZp; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729762AbfC2RD0 (ORCPT + 99 others); Fri, 29 Mar 2019 13:03:26 -0400 Received: from mail-wm1-f65.google.com ([209.85.128.65]:38129 "EHLO mail-wm1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729480AbfC2RD0 (ORCPT ); Fri, 29 Mar 2019 13:03:26 -0400 Received: by mail-wm1-f65.google.com with SMTP id w15so3623779wmc.3 for ; Fri, 29 Mar 2019 10:03:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4h7VtKuChw0e0QSGqGDCThC9qDFXbr94ocjisp/vP48=; b=DK5NTXZpVNhSYwXY6uVXLvL2a9EGSCpHjj2zbXUZ62yDuMlBg9mflXQZg0kAG2MrZs 9nmAmxFEmymZEgawOa5rWnJuOllBVJuuWZ7l9zLN2LV+2jx+/HABsGInQ3bAxHZcJZzh t4zMoNXo+xKuLihVE+WQSdDOP0jqcgNvrSsFu/lIE1ZuV2UNFtp76AWFqoTIlsRXmoyO GKkZ+PkS40YHjaG/9+BFvy31XwL7kY92eaY3xkBAPDgFciM6lmMz84fPCItFoHEc89J7 PYLHijgNub+HRTAKqz94pLzJM27mDR9DJdN7h2PFTuwomANJrn/96QgUD0XHIgfXE3AP wBGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4h7VtKuChw0e0QSGqGDCThC9qDFXbr94ocjisp/vP48=; b=oNX+8OLu/UJD5Y6rvpOINg1oTnjd5bvIRKmAOQkyRmeVlcG8hLsfXKXOMsf4heJIoM tgYmxKP+Gejb6cMDDdaECf+dC8UoRChmIKDindBY8cUVvGzGxIyG3S5OMsCQnnNZyp5z cZ/JoAuUMF+SMOpgoe88zEAc+qfGUM+lvP2b8MVn7hTMIFh11c8Bbm9PVlfUJBFZU8Z+ nX+V+Dhi5k5lM1tHY2Z41KEquCJi6ZhIFMzrza7JmMldnFeoTViWSsGwP8Pn6ruclU1K Fcp7RUwGnDo3aLG58uacdQda48x3gjMby/RN6p2y8eiZVlQDltF+wLZikNzJAU/50ADi brZA== X-Gm-Message-State: APjAAAVwtyr0vOjBkZdsgqjcdsm3Pu9q3DfqGJ2sCK/QSKQZ9Fnbw6yc Kv16agCIODHAMkGPNxZN9f4rpiPz2txXH1rh3M7L X-Received: by 2002:a7b:c3d7:: with SMTP id t23mr4151441wmj.62.1553879004012; Fri, 29 Mar 2019 10:03:24 -0700 (PDT) MIME-Version: 1.0 References: <20190325194220.5873-1-helgaas@kernel.org> <4faf234df19c1b54b70cbe82c0dacacc58568b87.camel@perches.com> In-Reply-To: <4faf234df19c1b54b70cbe82c0dacacc58568b87.camel@perches.com> From: Bjorn Helgaas Date: Fri, 29 Mar 2019 12:03:11 -0500 Message-ID: Subject: Re: [PATCH] vfio: Use dev_printk() when possible To: Joe Perches Cc: Bjorn Helgaas , Alex Williamson , kvm@vger.kernel.org, Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 25, 2019 at 3:49 PM Joe Perches wrote: > > On Mon, 2019-03-25 at 14:42 -0500, Bjorn Helgaas wrote: > > Use dev_printk() when possible to make messages consistent with other > > device-related messages. > > trivial note: > > > diff --git 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", > > + __func__); > > Many of these could use a colon after the %s used with __func__ > to make the output more consistent with other modules. Thanks, Joe. I added a colon to the two in vfio_platform_amdxgbe_reset(). Those were the only ones I saw, except for a couple "%s failed" messages in drivers/vfio/vfio_iommu_spapr_tce.c, which I didn't change because (1) they can't use dev_err() so slightly out of scope for this patch, and (2) it arguably reads more naturally without the colon. In vfio_pci.c, I converted some pr_info() to dev_info() without adding a dev_fmt definition, so that removed the KBUILD_MODNAME prefix, which I didn't intend. I'll add "#define dev_fmt pr_fmt" to restore the prefix. Messages from drivers/vfio use a variety of prefixes (none, "VFIO: ", KBUILD_MODNAME, __func__). That could potentially be rationalized but I would want Alex's guidance first. Bjorn