linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Noralf Trønnes" <noralf@tronnes.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Sam Ravnborg <sam@ravnborg.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: Eric Anholt <eric@anholt.net>, David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel@ffwll.ch>,
	David Lechner <david@lechnology.com>,
	Kamlesh Gurudasani <kamlesh.gurudasani@gmail.com>
Subject: Re: [PATCH v1 1/7] drm/st7735r: Avoid spamming logs if probe is deferred
Date: Tue, 27 Apr 2021 13:27:29 +0200	[thread overview]
Message-ID: <63e7b758-a1c0-db7c-6523-53d08c2f8726@tronnes.org> (raw)
In-Reply-To: <20210421163157.50949-1-andriy.shevchenko@linux.intel.com>



Den 21.04.2021 18.31, skrev Andy Shevchenko:
> The GPIO request can fail and probe may be deferred. Thus,
> the error message may be printed again and again. Avoid
> this by replacing DRM_DEV_ERROR() by dev_err_probe().
> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---

Series is applied to drm-misc-next.

Thanks,
Noralf.

      parent reply	other threads:[~2021-04-27 11:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 16:31 [PATCH v1 1/7] drm/st7735r: Avoid spamming logs if probe is deferred Andy Shevchenko
2021-04-21 16:31 ` [PATCH v1 2/7] drm/st7586: " Andy Shevchenko
2021-04-21 16:31 ` [PATCH v1 3/7] drm/mi0283qt: " Andy Shevchenko
2021-04-21 16:31 ` [PATCH v1 4/7] drm/ili9486: " Andy Shevchenko
2021-04-21 16:31 ` [PATCH v1 5/7] drm/ili9341: " Andy Shevchenko
2021-04-21 16:31 ` [PATCH v1 6/7] drm/ili9225: " Andy Shevchenko
2021-04-21 16:31 ` [PATCH v1 7/7] drm/hx8357d: " Andy Shevchenko
2021-04-27 11:27 ` Noralf Trønnes [this message]

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=63e7b758-a1c0-db7c-6523-53d08c2f8726@tronnes.org \
    --to=noralf@tronnes.org \
    --cc=airlied@linux.ie \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=david@lechnology.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric@anholt.net \
    --cc=kamlesh.gurudasani@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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).