From: Markus Elfring <Markus.Elfring@web.de>
To: Li Qiang <liqiang01@kylinos.cn>,
dri-devel@lists.freedesktop.org, Oded Gabbay <ogabbay@kernel.org>,
Tomeu Vizoso <tomeu@tomeuvizoso.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/rocket: Add scheds pointer to file_priv and fix memory leaks
Date: Tue, 25 Nov 2025 18:34:04 +0100 [thread overview]
Message-ID: <d2359ac1-f511-4080-8fc5-e3aa6af3011f@web.de> (raw)
In-Reply-To: <20251107024620.912403-1-liqiang01@kylinos.cn>
…
> This patch introduces a new …
Would a corresponding imperative wording become helpful for an improved change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc7#n94
Regards,
Markus
next prev parent reply other threads:[~2025-11-25 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 2:46 [PATCH] drm/rocket: Add scheds pointer to file_priv and fix memory leaks Li Qiang
2025-11-25 17:34 ` Markus Elfring [this message]
2025-12-09 7:04 ` Tomeu Vizoso
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=d2359ac1-f511-4080-8fc5-e3aa6af3011f@web.de \
--to=markus.elfring@web.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liqiang01@kylinos.cn \
--cc=ogabbay@kernel.org \
--cc=tomeu@tomeuvizoso.net \
/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;
as well as URLs for NNTP newsgroup(s).