From: Steven Rostedt <rostedt@goodmis.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
mmarek@suse.cz
Subject: Re: [PATCH] Use -mcount-record for dynamic ftrace
Date: Mon, 13 Apr 2015 18:03:47 -0400 [thread overview]
Message-ID: <20150413180347.6bfc0d5c@gandalf.local.home> (raw)
In-Reply-To: <20150413215508.GW15335@tassilo.jf.intel.com>
On Mon, 13 Apr 2015 14:55:08 -0700
Andi Kleen <ak@linux.intel.com> wrote:
> > Interesting. But I can't accept this until I can test it. I don't have
>
> AFAIK that's a unique policy. I don't think any other maintainer operates
> this way.
Um, really? Other maintainers don't test patches that they maintain?
This isn't like hardware that I don't have. This could certainly affect
people if it breaks, and I will be responsible to fix it. I'm not going
to do that until I have a setup where I can test things that break.
>
> > I wonder who's responsible for
> > https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/
> >
> > If they can add a i386/x86_64 build for gcc5 I'll be happy to download
> > it and test this patch.
>
> That doesn't make any sense.
>
What, adding gcc5 to the crosstools suite? Why not?
-- Steve
next prev parent reply other threads:[~2015-04-13 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 0:54 [PATCH] Use -mcount-record for dynamic ftrace Andi Kleen
2015-04-13 19:32 ` Steven Rostedt
2015-04-13 21:55 ` Andi Kleen
2015-04-13 22:03 ` Steven Rostedt [this message]
2015-04-13 22:54 ` Andi Kleen
2015-04-14 0:26 ` Steven Rostedt
2015-04-14 6:19 ` Kalle Valo
2015-04-14 13:07 ` Steven Rostedt
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=20150413180347.6bfc0d5c@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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