From: Raag Jadav <raag.jadav@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/dp: use seq buf for printing rates
Date: Wed, 27 Nov 2024 17:34:32 +0200 [thread overview]
Message-ID: <Z0c8CH-CYD7F8e9m@black.fi.intel.com> (raw)
In-Reply-To: <20241127131838.3268735-1-jani.nikula@intel.com>
On Wed, Nov 27, 2024 at 03:18:38PM +0200, Jani Nikula wrote:
> Hand rolling the buffer overflow handling with snprintf() is a bit
> tedious. The seq_buf interface is made for this. Switch to it.
>
> Use struct intel_display while at it.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 36 ++++++++++---------------
> 1 file changed, 14 insertions(+), 22 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 053a9a4182e7..4471c8fcd478 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -28,6 +28,7 @@
> #include <linux/export.h>
> #include <linux/i2c.h>
> #include <linux/notifier.h>
> +#include <linux/seq_buf.h>
> #include <linux/slab.h>
> #include <linux/sort.h>
> #include <linux/string_helpers.h>
> @@ -1506,41 +1507,32 @@ bool intel_dp_source_supports_tps4(struct drm_i915_private *i915)
> return DISPLAY_VER(i915) >= 10;
> }
>
> -static void snprintf_int_array(char *str, size_t len,
> - const int *array, int nelem)
> +static void seq_buf_print_array(struct seq_buf *s, const int *array, int nelem)
Perhaps with more users worth introducing as part of core lib?
Andy and I did something similar with kmemdup.
https://lore.kernel.org/linux-gpio/20241126172240.6044-1-raag.jadav@intel.com/
Raag
next prev parent reply other threads:[~2024-11-27 15:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 13:18 [PATCH] drm/i915/dp: use seq buf for printing rates Jani Nikula
2024-11-27 14:14 ` ✗ i915.CI.BAT: failure for " Patchwork
2024-11-28 13:03 ` Jani Nikula
2024-11-29 11:23 ` Illipilli, TejasreeX
2024-11-27 15:17 ` [PATCH] " Gustavo Sousa
2024-11-27 17:24 ` Jani Nikula
2024-11-27 18:04 ` Gustavo Sousa
2024-11-27 15:34 ` Raag Jadav [this message]
2024-11-27 17:06 ` Jani Nikula
2024-11-29 10:53 ` ✓ i915.CI.BAT: success for " Patchwork
2024-11-29 14:03 ` ✗ i915.CI.Full: failure " Patchwork
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=Z0c8CH-CYD7F8e9m@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox