From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Yonghao Zhang <hyz3367@gmail.com>
Cc: andersson@kernel.org, rishabhb@codeaurora.org,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remoteproc: sysfs: Fix stale coredump attribute documentation
Date: Tue, 15 Sep 2026 09:16:12 -0600 [thread overview]
Message-ID: <aqlhPFma-h9TjRc6@p14s> (raw)
In-Reply-To: <20260911030944.1645477-1-hyz3367@gmail.com>
On Fri, Sep 11, 2026 at 11:09:44AM +0800, Yonghao Zhang wrote:
> The documentation of the 'coredump' sysfs entry still advertises a
> "default" configuration option and describes it as the default value
> of the entry. Both date back to before the option was renamed to
> "enabled" and the default configuration was changed to "disabled".
>
> Update the comment to describe the three options the store callback
> actually accepts, "disabled", "enabled" and "inline", along with the
> real default value, and fix the coredump_show() comment which wrongly
> claims the configuration is exposed via debugfs.
>
> Fixes: bf41a0910cb2 ("remoteproc: Change default dump configuration to "disabled"")
> Assisted-by: Claude-Code:glm-5.3
> Signed-off-by: Yonghao Zhang <hyz3367@gmail.com>
> ---
> drivers/remoteproc/remoteproc_sysfs.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
I applied both of your patches.
Thanks,
Mathieu
> diff --git a/drivers/remoteproc/remoteproc_sysfs.c b/drivers/remoteproc/remoteproc_sysfs.c
> index 925b0cdbe577..c37736ff4acc 100644
> --- a/drivers/remoteproc/remoteproc_sysfs.c
> +++ b/drivers/remoteproc/remoteproc_sysfs.c
> @@ -76,7 +76,7 @@ static const char * const rproc_coredump_str[] = {
> [RPROC_COREDUMP_INLINE] = "inline",
> };
>
> -/* Expose the current coredump configuration via debugfs */
> +/* Expose the current coredump configuration via sysfs */
> static ssize_t coredump_show(struct device *dev,
> struct device_attribute *attr, char *buf)
> {
> @@ -87,14 +87,15 @@ static ssize_t coredump_show(struct device *dev,
>
> /*
> * By writing to the 'coredump' sysfs entry, we control the behavior of the
> - * coredump mechanism dynamically. The default value of this entry is "default".
> + * coredump mechanism dynamically. The default value of this entry is
> + * "disabled".
> *
> * The 'coredump' sysfs entry supports these commands:
> *
> * disabled: This is the default coredump mechanism. Recovery will proceed
> * without collecting any dump.
> *
> - * default: When the remoteproc crashes the entire coredump will be
> + * enabled: When the remoteproc crashes the entire coredump will be
> * copied to a separate buffer and exposed to userspace.
> *
> * inline: The coredump will not be copied to a separate buffer and the
> --
> 2.34.1
>
prev parent reply other threads:[~2026-09-15 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 3:09 Yonghao Zhang
2026-09-15 15:16 ` Mathieu Poirier [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=aqlhPFma-h9TjRc6@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=hyz3367@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=rishabhb@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®