All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>, linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 0/3] kernel-shark-qt: Merge kshark_load_data_records/entries()
Date: Wed, 4 Jul 2018 14:17:26 +0300	[thread overview]
Message-ID: <da0c7baa-2845-7873-3015-b250dd93e79e@gmail.com> (raw)
In-Reply-To: <20180703162130.082810105@goodmis.org>



On  3.07.2018 19:21, Steven Rostedt wrote:
> This works to consolidate the functions kshark_load_data_records()
> with kshark_load_data_entries(). It adds some helper functions
> for the two to use to simplify the code.
> 
> Note, doxygen warns that struct rec_list is not documented. Really?
> Such a simple structure doesn't really require documentation. Is
> there a way to shut it up? Or I can just add code to say
>   /** Shut doxygen up! ;-)

Yes, you can do

//! @cond Doxygen_Suppress

struct rec_list {
	struct pevent_record	*rec;
	struct rec_list		*next;
};

//! @endcond

Another solutions is to turn off all warnings. This can be done by adding

  WARN_IF_UNDOCUMENTED = NO

to doc/dox_config

On the other hand, do we expect the normal users to build doxygen 
documentation, if this documentation is available at 
http://kernelshark.org? So maybe we can tolerate having some warnings.

Actually this reminds me that there is a third solution. We can make 
this warnings invisible for the normal users by redirecting the 
doxygen's stderr to a file.

What do you think?

Yordan


> Yordan, please review these.
> 
> Steven Rostedt (VMware) (3):
>        kernel-shark-qt: Move declarations to top in datafilter.c example
>        kernel-shark-qt: Consolidate load_data_entries and load_data_records
>        kernel-shark-qt: Add helper function to find the next_cpu in kshark_load_data_*()
> 
> ----
>   kernel-shark-qt/examples/datafilter.c |   5 +-
>   kernel-shark-qt/src/libkshark.c       | 253 ++++++++++++++++++++--------------
>   2 files changed, 151 insertions(+), 107 deletions(-)
> 

  reply	other threads:[~2018-07-04 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 16:21 [PATCH 0/3] kernel-shark-qt: Merge kshark_load_data_records/entries() Steven Rostedt
2018-07-04 11:17 ` Yordan Karadzhov (VMware) [this message]
2018-07-04 11:26   ` Steven Rostedt
2018-07-04 11:49     ` Yordan Karadzhov (VMware)

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=da0c7baa-2845-7873-3015-b250dd93e79e@gmail.com \
    --to=y.karadz@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.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.