From: Joe Perches <joe@perches.com>
To: Wambui Karuga <wambui.karugax@gmail.com>,
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
Date: Thu, 07 Nov 2019 01:54:22 -0800 [thread overview]
Message-ID: <4c74db2614cefe23f888d0643c2d7c356086745a.camel@perches.com> (raw)
In-Reply-To: <20191107092945.15513-1-wambui.karugax@gmail.com>
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.
$ 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;
> }
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-07 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 9:29 [PATCH] drm/rockchip: use DRM_DEV_ERROR for log output Wambui Karuga
2019-11-07 9:54 ` Joe Perches [this message]
2019-11-07 13:38 ` Sean Paul
[not found] ` <20191108124630.GA10207@wambui>
2019-11-08 14:06 ` Heiko Stübner
2019-11-08 16:06 ` Sean Paul
2019-11-08 20:07 ` Wambui Karuga
2019-11-09 0:42 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4c74db2614cefe23f888d0643c2d7c356086745a.camel@perches.com \
--to=joe@perches.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=wambui.karugax@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).