public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: GeunSik Lim <leemgs1@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
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 14:37:28 +0900	[thread overview]
Message-ID: <49b7c2350906072237g163fc86bhc497183452de9a17@mail.gmail.com> (raw)
In-Reply-To: <20090608045353.GA11319@pengutronix.de>

2009/6/8 Uwe Kleine-König <u.kleine-koenig@pengutronix.de>:
>>          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>
Thank you for your advice and opinion about my trivital patch.
Sorry.  Maybe, I mistooked  about  how to append  "Reviewed-by tag".

>> + * 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.
Yes, It's correct.  But, I think that a detailed remark is not bad.

>
> 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.
Your comment is also correct.
Anyway, I want Clark to edit "debugfs/tracing" comment  with a suitable
expression normally.

-- 
Regards,
GeunSik Lim ( Samsung Electronics )
Blog : http://blog.naver.com/invain/
e-Mail: geunsik.lim@samsung.com
           leemgs@gmail.com , leemgs1@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
--
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

  reply	other threads:[~2009-06-08  5:37 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
2009-06-08  5:37       ` GeunSik Lim [this message]
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=49b7c2350906072237g163fc86bhc497183452de9a17@mail.gmail.com \
    --to=leemgs1@gmail.com \
    --cc=lclaudio@uudg.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    --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