From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: GeunSik Lim <leemgs1@gmail.com>
Cc: williams <williams@redhat.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
lclaudio@uudg.org
Subject: Re: [RESEND] [PATCH V2 ]cyclictest: fix invalid comment of debugfs mount directory.
Date: Mon, 8 Jun 2009 06:53:53 +0200 [thread overview]
Message-ID: <20090608045353.GA11319@pengutronix.de> (raw)
In-Reply-To: <1244425929.20635.90.camel@centos51>
Hi,
On Mon, Jun 08, 2009 at 10:52:09AM +0900, GeunSik Lim wrote:
> Dear Clark Williams,
>
> This is tracing(ftrace) directory's comment related patch file.
> Please, merge this patch.
>
>
>
> Regards,
> GeunSik Lim.
>
>
> Subject: [RESEND] [PATCH V2 ]cyclictest: Fix invalid comment of debugfs mount directory.
>
> The "debugfs/tracing" name is invalid as the mountpont of debugfs filesystem.
>
> For example,
> /sys/kernel/debug/tracing/ or
> /debug/tracing/ or
> /debugfs/tracing/ ...
>
> Fix directory name normally from debugfs/tracing to */tracing.
>
> Signed-off-by: GeunSik Lim <geunsik.lim@samsung.com>
> Reviewed-by : Luis Claudio R. Goncalves <lclaudio@uudg.org>
hhm, I don't know how Clark handles these flags, but I wouldn't count
the comments by Luis Claudio R. Goncalves as review. Still more as you
didn't follow his advice and I would only add this tag after the
reviewer is OK with the result.
<nitpick>
In the kernel the colons and names usually are not aligned.
</nitpick>
> ---
> src/cyclictest/cyclictest.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/src/cyclictest/cyclictest.c b/src/cyclictest/cyclictest.c
> index be9a3f9..2186de2 100644
> --- a/src/cyclictest/cyclictest.c
> +++ b/src/cyclictest/cyclictest.c
> @@ -179,7 +179,9 @@ static char functiontracer[MAX_PATH];
> static char traceroptions[MAX_PATH];
>
> /*
> - * Finds the path to the debugfs/tracing
> + * Finds the path to the tracing direcroty inside the default
s/direcroty/directory/
> + * mountpoint of debugfs filesystem.
> + * - debugfs related reference: http://lwn.net/Articles/334546/
set_debugfileprefix doesn't depend on a "default mountpoint", it parses
/proc/mounts, so it should even work if you mount it somewhere below /home.
And I'm not convinced that adding a link to lwn is a good idea. I would
expect that the normal cyclictest hacker knows about debugfs.
So what about simply
+ * Finds the tracing directory in a mounted debugfs.
? Ah, just see that is similar to the suggestion by Luis Claudio R.
Goncalves.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-08 4:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 2:06 [PATCH ]cyclictest: fix invalid comment of debugfs mount directory GeunSik Lim
2009-06-01 12:01 ` Luis Claudio R. Goncalves
2009-06-01 22:17 ` GeunSik Lim
2009-06-02 5:14 ` [PATCH V2 " GeunSik Lim
2009-06-08 1:52 ` [RESEND] " GeunSik Lim
2009-06-08 4:53 ` Uwe Kleine-König [this message]
2009-06-08 5:37 ` GeunSik Lim
2009-06-12 13:41 ` [PATCH] Make comment describing set_debugfileprefix a bit clearer Uwe Kleine-König
2009-06-12 15:36 ` Clark Williams
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=20090608045353.GA11319@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=lclaudio@uudg.org \
--cc=leemgs1@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
/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