From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Matt Merhar <mattmerhar@protonmail.com>,
Peter Geis <pgwipeout@gmail.com>,
Nicolas Chauvet <kwizart@gmail.com>
Cc: linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v14 1/2] drm/tegra: dc: Support memory bandwidth management
Date: Thu, 11 Mar 2021 20:12:35 +0300 [thread overview]
Message-ID: <37ff0499-6601-e97a-9fba-8e3e6f338b86@gmail.com> (raw)
In-Reply-To: <20210311170606.7543-2-digetx@gmail.com>
11.03.2021 20:06, Dmitry Osipenko пишет:
> +static const char * const tegra_plane_icc_names[TEGRA_DC_LEGACY_PLANES_NUM] = {
> + "wina", "winb", "winc", "", "", "", "cursor",
> +};
> +
> +int tegra_plane_interconnect_init(struct tegra_plane *plane)
> +{
> + const char *icc_name = tegra_plane_icc_names[plane->index];
> + struct device *dev = plane->dc->dev;
> + struct tegra_dc *dc = plane->dc;
> + int err;
> +
> + if (WARN_ON(plane->index >= TEGRA_DC_LEGACY_PLANES_NUM) ||
> + WARN_ON(!tegra_plane_icc_names[plane->index]))
> + return -EINVAL;
It just occurred to me that I added the NULL-check here, but missed to
change "" to NULLs. I'll make a v15 shortly.
next prev parent reply other threads:[~2021-03-11 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 17:06 [PATCH v14 0/2] Add memory bandwidth management to NVIDIA Tegra DRM driver Dmitry Osipenko
2021-03-11 17:06 ` [PATCH v14 1/2] drm/tegra: dc: Support memory bandwidth management Dmitry Osipenko
2021-03-11 17:12 ` Dmitry Osipenko [this message]
2021-03-11 17:06 ` [PATCH v14 2/2] drm/tegra: dc: Extend debug stats with total number of events Dmitry Osipenko
2021-03-11 17:09 ` [PATCH v14 0/2] Add memory bandwidth management to NVIDIA Tegra DRM driver 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=37ff0499-6601-e97a-9fba-8e3e6f338b86@gmail.com \
--to=digetx@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=kwizart@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mattmerhar@protonmail.com \
--cc=pgwipeout@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox