From: Jani Nikula <jani.nikula@linux.intel.com>
To: R Sundar <prosunofficial@gmail.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
imre.deak@intel.com, ville.syrjala@linux.intel.com,
R Sundar <prosunofficial@gmail.com>,
kernel test robot <lkp@intel.com>,
Julia Lawall <julia.lawall@inria.fr>
Subject: Re: [PATCH linux-next] drm/i915/dp: use string choice helpers
Date: Tue, 22 Oct 2024 13:26:35 +0300 [thread overview]
Message-ID: <87r088v3fo.fsf@intel.com> (raw)
In-Reply-To: <20241007174857.85061-1-prosunofficial@gmail.com>
On Mon, 07 Oct 2024, R Sundar <prosunofficial@gmail.com> wrote:
> Use str_on_off string helpers for better readability and to fix cocci
> warning.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Julia Lawall <julia.lawall@inria.fr>
> Closes: https://lore.kernel.org/r/202410071252.cWILJzrH-lkp@intel.com/
> Signed-off-by: R Sundar <prosunofficial@gmail.com>
Pushed to drm-intel-next, thanks for the patch.
BR,
Jani.
> ---
>
> Reported in linux repo:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> cocci warnings: (new ones prefixed by >>)
>>> drivers/gpu/drm/i915/display/intel_dp.c:2243:6-9: opportunity for str_on_off(dsc)
>
> vim +2243 drivers/gpu/drm/i915/display/intel_dp.c
>
> compile tested only.
>
> drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index fbb096be02ad..733619b14193 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -2475,7 +2475,7 @@ intel_dp_compute_config_link_bpp_limits(struct intel_dp *intel_dp,
> encoder->base.base.id, encoder->base.name,
> crtc->base.base.id, crtc->base.name,
> adjusted_mode->crtc_clock,
> - dsc ? "on" : "off",
> + str_on_off(dsc),
> limits->max_lane_count,
> limits->max_rate,
> limits->pipe.max_bpp,
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-10-22 10:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 17:48 [PATCH linux-next] drm/i915/dp: use string choice helpers R Sundar
2024-10-11 6:48 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2024-10-11 6:49 ` ✓ Fi.CI.BAT: success " Patchwork
2024-10-11 17:17 ` ✓ CI.Patch_applied: " Patchwork
2024-10-11 17:17 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-11 17:19 ` ✓ CI.KUnit: success " Patchwork
2024-10-11 17:30 ` ✓ CI.Build: " Patchwork
2024-10-11 17:32 ` ✓ CI.Hooks: " Patchwork
2024-10-11 17:34 ` ✗ CI.checksparse: warning " Patchwork
2024-10-11 18:14 ` ✓ CI.BAT: success " Patchwork
2024-10-11 20:38 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-10-11 23:38 ` ✗ CI.FULL: " Patchwork
2024-10-22 10:26 ` Jani Nikula [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=87r088v3fo.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=prosunofficial@gmail.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=ville.syrjala@linux.intel.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.