From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Javier Garcia <rampxxxx@gmail.com>,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
dakr@kernel.org, robin.clark@oss.qualcomm.com,
antomani103@gmail.com, dmitry.baryshkov@oss.qualcomm.com,
me@brighamcampbell.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] drm: Add directive to format code in comment
Date: Mon, 11 Aug 2025 08:04:39 +0700 [thread overview]
Message-ID: <aJlBp1MN7fnJmcTu@archie.me> (raw)
In-Reply-To: <20250810150706.305040-1-rampxxxx@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 328 bytes --]
On Sun, Aug 10, 2025 at 05:07:06PM +0200, Javier Garcia wrote:
> * The expected usage is:
> *
> + * .. code-block:: c
> + *
> * vm_bind {
> * struct drm_exec exec;
> *
LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-08-11 1:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 21:29 [PATCH] drm: Add directive to format code in comment Javier Garcia
2025-08-05 10:49 ` Dmitry Baryshkov
2025-08-05 11:51 ` Giant Sand Fans
2025-08-05 11:53 ` Giant Sand Fans
2025-08-05 16:55 ` Brigham Campbell
2025-08-05 17:55 ` Giant Sand Fans
2025-08-10 11:22 ` [PATCH v2] " Javier Garcia
2025-08-10 13:23 ` Danilo Krummrich
2025-08-10 14:12 ` Giant Sand Fans
2025-08-10 15:07 ` [PATCH v3] " Javier Garcia
2025-08-11 1:04 ` Bagas Sanjaya [this message]
2025-08-15 18:53 ` Danilo Krummrich
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=aJlBp1MN7fnJmcTu@archie.me \
--to=bagasdotme@gmail.com \
--cc=airlied@gmail.com \
--cc=antomani103@gmail.com \
--cc=dakr@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=me@brighamcampbell.com \
--cc=mripard@kernel.org \
--cc=rampxxxx@gmail.com \
--cc=robin.clark@oss.qualcomm.com \
--cc=simona@ffwll.ch \
--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.