From: Emil Velikov <emil.l.velikov@gmail.com>
To: Thierry Reding <treding@nvidia.com>
Cc: linux-tegra@vger.kernel.org, kernel@collabora.com,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm/tegra: remove irrelevant DRM_UNLOCKED flag
Date: Fri, 24 May 2019 16:19:52 +0100 [thread overview]
Message-ID: <20190524151952.GC8938@arch-x1c3> (raw)
In-Reply-To: <20190523091555.GA18130@ulmo>
On 2019/05/23, Thierry Reding wrote:
> On Wed, May 22, 2019 at 04:46:59PM +0100, Emil Velikov wrote:
> > From: Emil Velikov <emil.velikov@collabora.com>
> >
> > DRM_UNLOCKED doesn't do anything for non-legacy drivers. Remove it.
> >
> > Cc: Thierry Reding <treding@nvidia.com>
> > Cc: linux-tegra@vger.kernel.org
> > Cc: Daniel Vetter <daniel@ffwll.ch>
> > Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
> > ---
> > drivers/gpu/drm/tegra/drm.c | 28 ++++++++++++++--------------
> > 1 file changed, 14 insertions(+), 14 deletions(-)
>
> I assume you want to take this through drm-misc? In that case:
>
> Acked-by: Thierry Reding <treding@nvidia.com>
>
> Otherwise let me know and I'll pick it up into the Tegra tree.
>
Yes, I'll pick it up through drm-misc.
Thanks
Emil
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-05-24 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 15:46 [PATCH 1/4] drm/tegra: remove irrelevant DRM_UNLOCKED flag Emil Velikov
2019-05-22 15:47 ` [PATCH 2/4] drm/virtio: " Emil Velikov
2019-05-23 10:19 ` Gerd Hoffmann
2019-05-22 15:47 ` [PATCH 3/4] drm/i915: " Emil Velikov
2019-06-07 7:34 ` Daniel Vetter
2019-05-22 15:47 ` [PATCH 4/4] drm/TODO: add a task to kill DRM_UNLOCKED Emil Velikov
2019-05-22 16:12 ` Daniel Vetter
2019-05-24 15:17 ` Emil Velikov
2019-05-24 15:59 ` Daniel Vetter
2019-05-23 9:15 ` [PATCH 1/4] drm/tegra: remove irrelevant DRM_UNLOCKED flag Thierry Reding
2019-05-24 15:19 ` Emil Velikov [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=20190524151952.GC8938@arch-x1c3 \
--to=emil.l.velikov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-tegra@vger.kernel.org \
--cc=treding@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.