Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp2464630ybx; Fri, 8 Nov 2019 04:48:03 -0800 (PST) X-Google-Smtp-Source: APXvYqypnm4JTtjX+nf88h/1UQA5q5N2L3GE27X3yaLAp5R7HJIHNKiBHs8faRYyS8YtF5VoaIZU X-Received: by 2002:a50:85cb:: with SMTP id q11mr9692037edh.141.1573217283280; Fri, 08 Nov 2019 04:48:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573217283; cv=none; d=google.com; s=arc-20160816; b=zinjrL4x42roW2db5M4e+Hv+55+SUIdbND05/LnBI6jMnjTxwI5k0vCqu56I9X0Qk0 X57Skej7m6de91+nep6K4zuSpDAXz7Mh2z/w8+Glv0SRiuiC9MucpU1brxcABT3jYVNk QkkoTnaj5v3zx5lhyKSh/G/FgbOwe0qJJCV608yjGh37Sc+5OriSRJzV5FlMDVR4tRbU YCpNaahUeboskMgh1ih+GeY3kWDrpA/kMtw4pQZrxXoLHCVGk++kHZyujVULrPQicsbm lanEISmqY/VY+Haa2g7BXeMgSoq9pNb6zxwTtdsU7iRkh+5DyCKjl5Uu01WQUBIu8Zmj Mneg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:reply-to:message-id :subject:cc:to:from:date:dkim-signature; bh=5rxvla9MqG20qS8PvXLmnssk4K8x/Hmcm3O9O7mRXxw=; b=yENFgRHIapW1vSvbakPx1a3XQKtAGFqTVUwpxs+hqX/cQ+1HYKzgv5A5Nceuww/u10 AniA08Ej21M6avch4znPe7UMcazNLuYc8dRHWqn7Gkd509o0uR9xOorJWSzkb5GGGxHA O+rYMUeFtgNTzrnUEjcMXp3p1aEX9y5gL+dQYpFhPRfmAtolaB6lPSqyaKpMhxcXhDDI mujTUW2cPyxZ9UR/EtHkaTvfSK3A6pVyJNFGyL9Aa7TvNOZdsHmO6VXZ3KX0R10U74cK saY9aVZBpOZ6HawYUxYeMe8Mi7EVla4HEfuFEB7Oryewc+8OF+PhmScWqsfYhdc3nBxP MoeA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=uPGazBXt; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o22si3805779edv.175.2019.11.08.04.47.40; Fri, 08 Nov 2019 04:48:03 -0800 (PST) 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=@gmail.com header.s=20161025 header.b=uPGazBXt; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727210AbfKHMqo (ORCPT + 99 others); Fri, 8 Nov 2019 07:46:44 -0500 Received: from mail-pg1-f196.google.com ([209.85.215.196]:46852 "EHLO mail-pg1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726299AbfKHMqo (ORCPT ); Fri, 8 Nov 2019 07:46:44 -0500 Received: by mail-pg1-f196.google.com with SMTP id r18so3855799pgu.13 for ; Fri, 08 Nov 2019 04:46:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-disposition:in-reply-to:user-agent; bh=5rxvla9MqG20qS8PvXLmnssk4K8x/Hmcm3O9O7mRXxw=; b=uPGazBXt00dkMb4XcC5rtgD+hXWx7CX3wPcgEwLyc7/uLOfYxE6FYllxMnuz+mWElt TFD5nUaNmEAmii33SlcKmcwRB/VpqoHROLQX9ZyCrtx9I4iBwX8+lYIDPNfhEfijDRba bgcv/EsdA1DP+E5Hrr68Xo4mcflJRzSKf1MMQV10Dg+1kcWGz90yKhlmkk11yAfexpqx 0dL1pT6VkNqhUK5pZzP1sxhyhWIrBVnYdFEDS5ZRUp5L6g4sixLzlXeJSblLGsL8+M+K g9JsPudijfoCeT2BTdTQukwx+LJytsnw6bdwQ/QAf/tWC8Qgm7SY9Efvhhs+ViecTSzM YUFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:reply-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=5rxvla9MqG20qS8PvXLmnssk4K8x/Hmcm3O9O7mRXxw=; b=C3UqMbNCcp+ImtV8BqBL7r8YMahcoVOy+0j1IrWYaHKXRf2oBaErK3MLqjL5ev6Ylf y6PGbcfk3PPuYdjDnRDHWsFGvZX3pbinSVVVmCjVKpxR4vXpIy16cZeHD3+XSk1Rphp6 uoZaxPqVtFr8YtPcru09tpm2I5wAk2lzHknnNxM978Wl6TPh1X6jO4UYJQrbOhJuLcWe d138FvPBqCWzB8kDNMa9Usa/KGUmF/IGRU76nhtAhgSoS5+AKuktsX/0i8RwxdQATwRW pYvLPDIRiSiWoBwzyukJOQWaxJLhEsNS/MxqLPE6bquYkUbwoIMnW455U+kS7ZeL0L9Q uYrg== X-Gm-Message-State: APjAAAVApbXGzf58i1mx1FuYiunAfEQDHuaA23YxW/0L236nSlnS6klT dUws6RkyyqC2uYB0AMVd8AqAxf4puswSTg== X-Received: by 2002:a17:90a:c004:: with SMTP id p4mr8684007pjt.104.1573217203600; Fri, 08 Nov 2019 04:46:43 -0800 (PST) Received: from wambui ([197.254.95.38]) by smtp.gmail.com with ESMTPSA id n23sm5601302pff.137.2019.11.08.04.46.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 08 Nov 2019 04:46:42 -0800 (PST) Date: Fri, 8 Nov 2019 15:46:30 +0300 From: Wambui Karuga To: Sean Paul Cc: hjc@rock-chips.com, heiko@sntech.de, airlied@linux.ie, daniel@ffwll.ch, dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] drm/rockchip: use DRM_DEV_ERROR for log output Message-ID: <20191108124630.GA10207@wambui> Reply-To: 20191107133851.GF63329@art_vandelay References: <20191107092945.15513-1-wambui.karugax@gmail.com> <4c74db2614cefe23f888d0643c2d7c356086745a.camel@perches.com> <20191107133851.GF63329@art_vandelay> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191107133851.GF63329@art_vandelay> User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 07, 2019 at 08:38:51AM -0500, Sean Paul wrote: > On Thu, Nov 07, 2019 at 01:54:22AM -0800, Joe Perches wrote: > > On Thu, 2019-11-07 at 12:29 +0300, Wambui Karuga wrote: > > > Replace the use of the dev_err macro with the DRM_DEV_ERROR > > > DRM helper macro. > > > > The commit message should show the reason _why_ you are doing > > this instead of just stating that you are doing this. > > > > It's not that dev_err is uncommon in drivers/gpu/drm. > > > > It is uncommon (this is the sole instance) in rockchip, however. So it makes > sense to convert the dev_* prints in rockchip to DRM_DEV for consistency. > > Wambui, could you also please convert the dev_warn instance as well? > Hey, Sean. Trying to convert this dev_warn instance, but the corresponding DRM_WARN macro does not take the dev parameter which seems to be useful in the original output. Should I still convert it to DRM_WARN without the hdmi->dev parameter? Thanks, wambui > I'll apply this to drm-misc-next and expand on the commit message a bit. > > Thanks, > > Sean > > > $ git grep -w dev_err drivers/gpu/drm | wc -l > > 1950 > > $ git grep -w DRM_DEV_ERROR drivers/gpu/drm | wc -l > > 756 > > > > > diff --git a/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c b/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c > > [] > > > @@ -916,7 +916,7 @@ static int dw_mipi_dsi_rockchip_probe(struct platform_device *pdev) > > > } > > > > > > if (!dsi->cdata) { > > > - dev_err(dev, "no dsi-config for %s node\n", np->name); > > > + DRM_DEV_ERROR(dev, "no dsi-config for %s node\n", np->name); > > > return -EINVAL; > > > } > > > > > > > > _______________________________________________ > > dri-devel mailing list > > dri-devel@lists.freedesktop.org > > https://lists.freedesktop.org/mailman/listinfo/dri-devel > > -- > Sean Paul, Software Engineer, Google / Chromium OS