From: Sam Ravnborg <sam@ravnborg.org>
To: Bernard Zhao <bernard@vivo.com>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
opensource.kernel@vivo.com
Subject: Re: [PATCH] drm/via: reduce no need mutex_lock area
Date: Sat, 17 Oct 2020 10:11:32 +0200 [thread overview]
Message-ID: <20201017081132.GD2568873@ravnborg.org> (raw)
In-Reply-To: <20200814083021.8962-1-bernard@vivo.com>
Hi Bernard.
On Fri, Aug 14, 2020 at 01:30:19AM -0700, Bernard Zhao wrote:
> In function via_mem_alloc`s error branch, DRM_ERROR is protected
> in the mutex_lock(&dev->struct_mutex) area.
> >From the code, we see that DRM_ERROR is just an error log print
> without any struct element, there is no need to protect this.
>
> Signed-off-by: Bernard Zhao <bernard@vivo.com>
Thanks, applied to drm-misc-next.
The patch will show up in -next in a few weeks.
Sam
prev parent reply other threads:[~2020-10-17 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 8:30 [PATCH] drm/via: reduce no need mutex_lock area Bernard Zhao
2020-10-17 8:11 ` Sam Ravnborg [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=20201017081132.GD2568873@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=bernard@vivo.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=opensource.kernel@vivo.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