linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>
Subject: Re: [PATCH] tracefs: Remove kerneldoc from struct eventfs_file
Date: Tue, 22 Aug 2023 21:48:08 +0900	[thread overview]
Message-ID: <20230822214808.6da2059746218d93fa6bfe0e@kernel.org> (raw)
In-Reply-To: <20230822053313.77aa3397@rorschach.local.home>

On Tue, 22 Aug 2023 05:33:13 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> From d0d094090c093499380049c413b8f1c5b995ff52 Mon Sep 17 00:00:00 2001
> From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
> Date: Tue, 22 Aug 2023 05:29:22 -0400
> Subject: [PATCH] tracefs: Remove kerneldoc from struct eventfs_file
> 
> The struct eventfs_file is a local structure and should not be parsed by
> kernel doc. It also does not fully follow the kerneldoc format and is
> causing kerneldoc to spit out errors. Replace the /** to /* so that
> kerneldoc no longer processes this structure.
> 
> Also format the comments of the delete union of the structure to be a bit
> better.

Looks good to me.

Reviewed-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>

Thanks,
> 
> Link: https://lore.kernel.org/linux-trace-kernel/20230818201414.2729745-1-willy@infradead.org/
> 
> Reported-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
>  fs/tracefs/event_inode.c | 14 ++++++++++----
>  1 file changed, 10 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/tracefs/event_inode.c b/fs/tracefs/event_inode.c
> index da8d2e73cc47..237c6f370ad9 100644
> --- a/fs/tracefs/event_inode.c
> +++ b/fs/tracefs/event_inode.c
> @@ -27,7 +27,7 @@ struct eventfs_inode {
>  	struct list_head	e_top_files;
>  };
>  
> -/**
> +/*
>   * struct eventfs_file - hold the properties of the eventfs files and
>   *                       directories.
>   * @name:	the name of the file or directory to create
> @@ -48,10 +48,16 @@ struct eventfs_file {
>  	struct eventfs_inode		*ei;
>  	const struct file_operations	*fop;
>  	const struct inode_operations	*iop;
> +	/*
> +	 * Union - used for deletion
> +	 * @del_list:	list of eventfs_file to delete
> +	 * @rcu:	eventfs_file to delete in RCU
> +	 * @is_freed:	node is freed if one of the above is set
> +	 */
>  	union {
> -		struct list_head	del_list; /* list of eventfs_file to delete */
> -		struct rcu_head		rcu; /* eventfs_file to delete */
> -		unsigned long		is_freed; /* Freed if one of the above is set */
> +		struct list_head	del_list;
> +		struct rcu_head		rcu;
> +		unsigned long		is_freed;
>  	};
>  	void				*data;
>  	umode_t				mode;
> -- 
> 2.40.1
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2023-08-22 12:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22  9:33 [PATCH] tracefs: Remove kerneldoc from struct eventfs_file Steven Rostedt
2023-08-22 12:48 ` Masami Hiramatsu [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=20230822214808.6da2059746218d93fa6bfe0e@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rostedt@goodmis.org \
    --cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).