From: Natalie Vock <nat@pixelcluster.dev>
To: Manush Prajwal <manushprajwal555@gmail.com>,
Maarten Lankhorst <dev@lankhorst.se>,
Maxime Ripard <mripard@kernel.org>
Cc: cgroups@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] cgroup/dmem: fix comment typos in dmem.c
Date: Wed, 2 Sep 2026 12:10:40 +0200 [thread overview]
Message-ID: <d1e18ac8-b1fb-4ab8-9fc6-d740db710d70@pixelcluster.dev> (raw)
In-Reply-To: <20260813104236.1532-1-manushprajwal555@gmail.com>
Hi,
On 8/13/26 12:42, Manush Prajwal wrote:
> Fix "succesful" -> "successful" (x2) in the kernel-doc for
> dmem_cgroup_region::ref and dmem_cgroup_try_charge(). No functional
> change.
>
> Signed-off-by: Manush Prajwal <manushprajwal555@gmail.com>
Reviewed-by: Natalie Vock <nat@pixelcluster.dev>
and applied to drm-misc-next. Thank you!
Best,
Natalie
> ---
> kernel/cgroup/dmem.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/cgroup/dmem.c b/kernel/cgroup/dmem.c
> index 4753a67d0f..342ea5324e 100644
> --- a/kernel/cgroup/dmem.c
> +++ b/kernel/cgroup/dmem.c
> @@ -21,7 +21,7 @@
> struct dmem_cgroup_region {
> /**
> * @ref: References keeping the region alive.
> - * Keeps the region reference alive after a succesful RCU lookup.
> + * Keeps the region reference alive after a successful RCU lookup.
> */
> struct kref ref;
>
> @@ -634,7 +634,7 @@ EXPORT_SYMBOL_GPL(dmem_cgroup_uncharge);
> * dmem_cgroup_try_charge() - Try charging a new allocation to a region.
> * @region: dmem region to charge
> * @size: Size (in bytes) to charge.
> - * @ret_pool: On succesfull allocation, the pool that is charged.
> + * @ret_pool: On successful allocation, the pool that is charged.
> * @ret_limit_pool: On a failed allocation, the limiting pool.
> *
> * This function charges the @region region for a size of @size bytes.
prev parent reply other threads:[~2026-09-02 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 10:42 [PATCH] cgroup/dmem: fix comment typos in dmem.c Manush Prajwal
2026-09-02 10:10 ` Natalie Vock [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=d1e18ac8-b1fb-4ab8-9fc6-d740db710d70@pixelcluster.dev \
--to=nat@pixelcluster.dev \
--cc=cgroups@vger.kernel.org \
--cc=dev@lankhorst.se \
--cc=dri-devel@lists.freedesktop.org \
--cc=manushprajwal555@gmail.com \
--cc=mripard@kernel.org \
/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.