From: Jyri Sarha <jsarha@ti.com>
To: Daniel Schultz <d.schultz@phytec.de>, <airlied@linux.ie>,
<tomi.valkeinen@ti.com>, <dri-devel@lists.freedesktop.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] drm: tilcdc: Correct misspelling in error message
Date: Mon, 31 Oct 2016 19:33:35 +0200 [thread overview]
Message-ID: <04d8a90d-537d-6912-e554-2cedb61c0ae1@ti.com> (raw)
In-Reply-To: <1477655562-19642-2-git-send-email-d.schultz@phytec.de>
On 10/28/16 14:52, Daniel Schultz wrote:
> This error message will be printed when a FIFO underflow irq has
> triggered. Since this happens sometimes and the error message will be
> displayed on the console, it should have a correct spelling.
>
> Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
Picked up for my next pull request.
Best regards,
Jyri
> ---
> drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/tilcdc/tilcdc_crtc.c b/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
> index fe1d088..63caed4 100644
> --- a/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
> +++ b/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
> @@ -769,7 +769,7 @@ irqreturn_t tilcdc_crtc_irq(struct drm_crtc *crtc)
> }
>
> if (stat & LCDC_FIFO_UNDERFLOW)
> - dev_err_ratelimited(dev->dev, "%s(0x%08x): FIFO underfow",
> + dev_err_ratelimited(dev->dev, "%s(0x%08x): FIFO underflow",
> __func__, stat);
>
> /* For revision 2 only */
>
next prev parent reply other threads:[~2016-10-31 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 11:52 [PATCH 1/2] drm: tilcdc: Add revision handling for FB_CEILING Daniel Schultz
2016-10-28 11:52 ` [PATCH 2/2] drm: tilcdc: Correct misspelling in error message Daniel Schultz
2016-10-31 17:33 ` Jyri Sarha [this message]
2016-10-31 17:37 ` Jyri Sarha
2016-10-31 17:33 ` [PATCH 1/2] drm: tilcdc: Add revision handling for FB_CEILING Jyri Sarha
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=04d8a90d-537d-6912-e554-2cedb61c0ae1@ti.com \
--to=jsarha@ti.com \
--cc=airlied@linux.ie \
--cc=d.schultz@phytec.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomi.valkeinen@ti.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