[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0810230646170.31277@gandalf.stny.rr.com>
Date: Thu, 23 Oct 2008 06:49:58 -0400 (EDT)
From: Steven Rostedt <rostedt@...dmis.org>
To: Wenji Huang <wenji.huang@...cle.com>
cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
Frederic Weisbecker <fweisbec@...il.com>,
Abhishek Sagar <sagar.abhishek@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 00/13 v2] ftrace: clean ups and fixes
On Thu, 23 Oct 2008, Wenji Huang wrote:
> Hi,
> just several trivial things.
Thanks,
>
> [PATCH 02/13 v2] ftrace: dynamic ftrace process only text section
> +# Acceptible sections to record.
>
> typo - Acceptible
Ah, it should be Acceptable.
>
> [PATCH 03/13 v2] ftrace: return error on failed modified text.
> + * This is a very sensitive operatation and great care needs
>
> typo - operatation
Sorry, I must have stuttered ;-)
> Why not put comments to function definition?
The function is arch dependent. And the comment here is also to help
the arch maintainers know what is needed of that function.
>
> [PATCH 04/13 v2] ftrace: comment arch ftrace code
> + * as well as code changing. We do this by using the
> + * __copy_*_user functions.
>
> According to [PATCH 05/13], change to using the proper API for reading and
> writing, not __copy_*_user.
Good catch. Thanks,
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists