mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Guowen Li" <guowen.li.linux@gmail.com>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix compiler warning in ftrace.c
Date: Fri, 3 Jun 2011 12:52:59 +0800	[thread overview]
Message-ID: <B4B144EDA1BA4138AFAC732D06C60F8B@WWW67E861F6858> (raw)
In-Reply-To: <1307069404.3667.35.camel@gandalf.stny.rr.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 1492 bytes --]

Thank you for pointing them out, i will be careful next time. :)

Signed-off-by: Guowen Li <guowen.li.linux@gmail.com>
----- Original Message ----- 
From: "Steven Rostedt" <rostedt@goodmis.org>
To: "GuoWen Li" <guowen.li.linux@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Friday, June 03, 2011 10:50 AM
Subject: Re: [PATCH] Fix compiler warning in ftrace.c


> Couple of things:
> 
> On Wed, 2011-06-01 at 19:18 +0800, GuoWen Li wrote:
>> kernel/trace/ftrace.c: In function ‘ftrace_regex_write.clone.15’:
>> kernel/trace/ftrace.c:2743:6: warning: ‘ret’ may be used uninitialized in this 
>> function
>> 
>> Signed-off-by: GuoWen Li
> 
> Please add your mail address to your SOB. (I'll fix it)
> 
>> ---
>>  kernel/trace/ftrace.c |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>> 
>> diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
>> index 1ee417f..204b3eb 100644
>> --- a/kernel/trace/ftrace.c
>> +++ b/kernel/trace/ftrace.c
>> @@ -2740,7 +2740,7 @@ static int ftrace_process_regex(struct ftrace_hash 
>> *hash,
>>  {
>>         char *func, *command, *next = buff;
>>         struct ftrace_func_command *p;
>> -       int ret;
>> +       int ret = -EINVAL;
> 
> This patch has horrible white space issues. (I fixed it)
> 
> -- Steve
> 
> 
>>  
>>         func = strsep(&next, ":");
> 
> 
>ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  reply	other threads:[~2011-06-03  4:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 11:18 GuoWen Li
2011-06-03  2:45 ` Steven Rostedt
2011-06-03  2:50 ` Steven Rostedt
2011-06-03  4:52   ` Guowen Li [this message]
2011-06-08 18:34 ` [tip:perf/urgent] ftrace: Fix possible undefined return code tip-bot for GuoWen Li

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=B4B144EDA1BA4138AFAC732D06C60F8B@WWW67E861F6858 \
    --to=guowen.li.linux@gmail.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®