From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: Mallesh Koujalagi <mallesh.koujalagi@intel.com>,
<dri-devel@lists.freedesktop.org>, <andrealmeid@igalia.com>,
<christian.koenig@amd.com>, <airlied@gmail.com>,
<simona.vetter@ffwll.ch>, <mripard@kernel.org>,
<maarten.lankhorst@linux.intel.com>, <tzimmermann@suse.de>,
<anshuman.gupta@intel.com>, <badal.nilawar@intel.com>,
<riana.tauro@intel.com>, <karthik.poosa@intel.com>,
<sk.anirban@intel.com>, <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v6] drm/drv: Convert wedged event string building to seq_buf
Date: Mon, 24 Aug 2026 16:35:44 -0400 [thread overview]
Message-ID: <aoyrIJNnj5U5JsFE@intel.com> (raw)
In-Reply-To: <aop1P1xK9fB90AzQ@black.igk.intel.com>
On Sun, Aug 23, 2026 at 06:21:19AM +0200, Raag Jadav wrote:
> On Sun, Aug 23, 2026 at 06:03:50AM +0530, Mallesh Koujalagi wrote:
> > event_string[] has a fixed size of WEDGE_STR_LEN (32) bytes.
> > The original scnprintf()-based loop required a manual pre-flight
> > bounds check.
> >
> > Replace the manual bookkeeping with seq_buf, which tracks overflow
> > internally. seq_buf_printf() writes each "method," token into the
> > buffer.
> >
> > On overflow, a warning is issued, len retains the position of the
> > last successful write, so the trailing comma is stripped cleanly
> > without including any partial method name in the uevent payload.
> >
> > Assisted-by: Claude:claude-Sonnet-4.6
> > Signed-off-by: Mallesh Koujalagi <mallesh.koujalagi@intel.com>
>
> Reviewed-by: Raag Jadav <raag.jadav@intel.com>
pushed to drm-misc-next
prev parent reply other threads:[~2026-08-24 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 0:33 [PATCH v6] drm/drv: Convert wedged event string building to seq_buf Mallesh Koujalagi
2026-08-23 4:21 ` Raag Jadav
2026-08-24 20:35 ` Rodrigo Vivi [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=aoyrIJNnj5U5JsFE@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=andrealmeid@igalia.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=karthik.poosa@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mallesh.koujalagi@intel.com \
--cc=mripard@kernel.org \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=simona.vetter@ffwll.ch \
--cc=sk.anirban@intel.com \
--cc=tzimmermann@suse.de \
/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.