From: "Maxime Ripard" <mripard@kernel.org>
To: "Jared Kangas" <jkangas@redhat.com>
Cc: Brian.Starkey@arm.com, benjamin.gaignard@collabora.com,
christian.koenig@amd.com, dri-devel@lists.freedesktop.org,
jstultz@google.com, linaro-mm-sig@lists.linaro.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
mripard@kernel.org, sumit.semwal@linaro.org,
tjmercier@google.com, "Maxime Ripard" <mripard@kernel.org>
Subject: Re: [PATCH v3 1/3] Documentation: dma-buf: heaps: Fix code markup
Date: Tue, 27 May 2025 12:59:41 +0000 [thread overview]
Message-ID: <b1b422178ef37cf1629dc18cbe5344c6@kernel.org> (raw)
In-Reply-To: <20250522191418.442390-2-jkangas@redhat.com>
On Thu, 22 May 2025 12:14:16 -0700, Jared Kangas wrote:
> Code snippets should be wrapped in double backticks to follow
> reStructuredText semantics; the use of single backticks uses the
> :title-reference: role by default, which isn't quite what we want.
> Add double backticks to code snippets to fix this.
>
>
> [ ... ]
Reviewed-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
next prev parent reply other threads:[~2025-05-27 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 19:14 [PATCH v3 0/3] dma-buf: heaps: Use constant name for CMA heap Jared Kangas
2025-05-22 19:14 ` [PATCH v3 1/3] Documentation: dma-buf: heaps: Fix code markup Jared Kangas
2025-05-27 12:59 ` Maxime Ripard [this message]
2025-05-22 19:14 ` [PATCH v3 2/3] dma-buf: heaps: Parameterize heap name in __add_cma_heap() Jared Kangas
2025-05-27 13:00 ` Maxime Ripard
2025-05-22 19:14 ` [PATCH v3 3/3] dma-buf: heaps: Give default CMA heap a fixed name Jared Kangas
2025-05-27 13:05 ` Maxime Ripard
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=b1b422178ef37cf1629dc18cbe5344c6@kernel.org \
--to=mripard@kernel.org \
--cc=Brian.Starkey@arm.com \
--cc=benjamin.gaignard@collabora.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jkangas@redhat.com \
--cc=jstultz@google.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tjmercier@google.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.