From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] drm/tegra: gr2d: Explicitly control module reset
Date: Thu, 8 Jul 2021 18:19:42 +0300 [thread overview]
Message-ID: <620f948d-4871-e038-8d35-40308bad01b1@gmail.com> (raw)
In-Reply-To: <d9112247-ce69-9281-75e6-6cb3296d19a7@gmail.com>
08.07.2021 18:13, Dmitry Osipenko пишет:
>> #include "drm.h"
>> #include "gem.h"
>> @@ -19,6 +21,7 @@ struct gr2d_soc {
>> struct gr2d {
>> struct tegra_drm_client client;
>> struct host1x_channel *channel;
>> + struct reset_control *rst;
> Unused variable?
Ah, I haven't noticed that it's struct. Looks okay.
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/tegra: gr2d: Explicitly control module reset
Date: Thu, 8 Jul 2021 18:19:42 +0300 [thread overview]
Message-ID: <620f948d-4871-e038-8d35-40308bad01b1@gmail.com> (raw)
In-Reply-To: <d9112247-ce69-9281-75e6-6cb3296d19a7@gmail.com>
08.07.2021 18:13, Dmitry Osipenko пишет:
>> #include "drm.h"
>> #include "gem.h"
>> @@ -19,6 +21,7 @@ struct gr2d_soc {
>> struct gr2d {
>> struct tegra_drm_client client;
>> struct host1x_channel *channel;
>> + struct reset_control *rst;
> Unused variable?
Ah, I haven't noticed that it's struct. Looks okay.
next prev parent reply other threads:[~2021-07-08 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 14:37 [PATCH] drm/tegra: gr2d: Explicitly control module reset Thierry Reding
2021-07-08 14:37 ` Thierry Reding
2021-07-08 15:13 ` Dmitry Osipenko
2021-07-08 15:13 ` Dmitry Osipenko
2021-07-08 15:19 ` Dmitry Osipenko [this message]
2021-07-08 15:19 ` Dmitry Osipenko
2021-07-08 19:40 ` Dmitry Osipenko
2021-07-08 19:40 ` Dmitry Osipenko
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=620f948d-4871-e038-8d35-40308bad01b1@gmail.com \
--to=digetx@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@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 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.