public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel: trace: remove __init from race_selftest_startup_function() and trace_selftest_startup_function_graph()
Date: Tue, 16 Jul 2013 08:22:15 +0800	[thread overview]
Message-ID: <51E49236.6080600@asianux.com> (raw)
In-Reply-To: <1373905251.17876.150.camel@gandalf.local.home>

On 07/16/2013 12:20 AM, Steven Rostedt wrote:
> On Mon, 2013-07-15 at 10:12 +0800, Chen Gang wrote:
> 
>> > Hello Frederic and Ingo:
> Are you trying to go around me? I wrote this code and I'm one of the
> maintainers for it. Your issue is very minor, and can wait till other
> things get done first.
> 
> You said my previous patch fixed your problem, right? Then I'll add your
> tested by and push it in due course.
> 
> I'll also get around to adding __init's to other functions too. But it
> is *very* low on the totem pole of importance.
> 

I only provide my suggestions (or recommendations) which I think might
be useful for us, and I don't care about whether you accept or not.

If you want discuss, we can continue, if you won't (now, I guess so),
you can just provide your choice is OK.

>> > 
>> > Could you provide your suggestions or completions for it ?
>> > 
>> > The trace_selftest_startup_* funcitons are mostly added by you without
>> > '__init', do you have additional considerations about it (intend to have
>> > no '__init') ?
>> > 
>> > If no reply, I recommend to keep no '__init': apply this patch or
>> > regress part of the patch "f1ed7c7 ftrace: Do not run selftest if
>> > command line parameter is set" (at least, it can avoid related warnings
>> > and treat all *selftest* fair).
> It's a compile time warning that's a false positive. Not a run time
> crash or other issue of importance. It can wait, relax. Otherwise you
> are starting to become annoying.

At least this patch is not 'urgent' (not a run time crash, or other
issue of 'urgent'), but every members have their own opinions to treat
this issue whether 'important' or not ('important' != 'urgent').

And every members' time resources are expensive (not only you, but also
me, and other members).

When I got none-reply, I don't know what happened (whether you agree, or
not, what I said correct or incorrect ?), it is a polite to give a
confirmation reply to tell whether you accept or not.


Thanks.
-- 
Chen Gang

  reply	other threads:[~2013-07-16  0:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11  0:31 [PATCH] kernel: trace: remove __init from race_selftest_startup_function() and trace_selftest_startup_function_graph() Chen Gang
2013-07-11 16:47 ` Steven Rostedt
2013-07-11 23:51   ` Chen Gang
2013-07-12  1:41     ` Steven Rostedt
2013-07-12  1:58       ` Chen Gang
2013-07-12  2:38         ` Steven Rostedt
2013-07-12  3:04           ` Chen Gang
2013-07-12  7:20             ` Chen Gang
2013-07-15  2:12               ` Chen Gang
2013-07-15 16:20                 ` Steven Rostedt
2013-07-16  0:22                   ` Chen Gang [this message]
2013-07-17  0:52                     ` Chen Gang

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=51E49236.6080600@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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