[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4f7f992f-0c68-4760-ac9d-37a5c6c948cd@kernel.org>
Date: Fri, 17 May 2024 12:18:58 +0200
From: Daniel Bristot de Oliveira <bristot@...nel.org>
To: Yang Li <yang.lee@...ux.alibaba.com>, rostedt@...dmis.org,
mhiramat@...nel.org
Cc: linux-trace-kernel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] rv: Update rv_en(dis)able_monitor doc to match
kernel-doc
Hi Yang
On 5/17/24 11:14, Yang Li wrote:
> The patch updates the function documentation comment for
> rv_en(dis)able_monitor to adhere to the kernel-doc specification.
>
> Signed-off-by: Yang Li <yang.lee@...ux.alibaba.com>
> ---
> kernel/trace/rv/rv.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/kernel/trace/rv/rv.c b/kernel/trace/rv/rv.c
> index 2f68e93fff0b..df0745a42a3f 100644
> --- a/kernel/trace/rv/rv.c
> +++ b/kernel/trace/rv/rv.c
> @@ -245,6 +245,7 @@ static int __rv_disable_monitor(struct rv_monitor_def *mdef, bool sync)
>
> /**
> * rv_disable_monitor - disable a given runtime monitor
> + * @mdef: Pointer to the monitor definition structure.
This change is in for mainline kernel, why are you using the -next on the Subject?
-- Daniel
Powered by blists - more mailing lists