From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <treding@nvidia.com>
Cc: kbuild-all@lists.01.org, dri-devel@lists.freedesktop.org,
linux-tegra@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [tegra-drm:drm/tegra/for-next 16/17] drivers/gpu/drm/tegra/dc.c:1843:53: warning: variable 'new_dc_state' set but not used
Date: Fri, 13 Aug 2021 20:16:34 +0300 [thread overview]
Message-ID: <167372e5-1d16-9da4-941e-848209d9e828@gmail.com> (raw)
In-Reply-To: <6a4b2b81-cf37-5a0b-bb6a-4857d1a4ffc5@gmail.com>
13.08.2021 20:12, Dmitry Osipenko пишет:
...
> I probably should update compiler or set W=1 to get that warning. These variables were used in older versions of the patch and they can be removed now.
>
> Please amend the patch with this:
Perhaps too late already. I'll make patch for that and then also check
whether the UAPI patches were fixed.
prev parent reply other threads:[~2021-08-13 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 16:36 [tegra-drm:drm/tegra/for-next 16/17] drivers/gpu/drm/tegra/dc.c:1843:53: warning: variable 'new_dc_state' set but not used kernel test robot
2021-08-13 17:12 ` Dmitry Osipenko
2021-08-13 17:16 ` Dmitry Osipenko [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=167372e5-1d16-9da4-941e-848209d9e828@gmail.com \
--to=digetx@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lkp@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox