From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: "Martin Liška" <mliska@suse.cz>,
linux-kernel@vger.kernel.org, "Ingo Molnar" <mingo@redhat.com>,
"Paul Mackerras" <paulus@samba.org>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] perf: fix wrong DEBUG configuration
Date: Mon, 25 May 2015 20:32:46 +0200 [thread overview]
Message-ID: <20150525183246.GA21153@gmail.com> (raw)
In-Reply-To: <20150525135238.GE17970@kernel.org>
* Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> Em Mon, May 25, 2015 at 01:12:44PM +0200, Martin Liška escreveu:
> > On 05/25/2015 01:09 PM, Ingo Molnar wrote:
> > >
> > >* Martin Liška <mliska@suse.cz> wrote:
> > >
> > >>>>Right optimize debugging experience is given by passing -Og to
> > >>>>compiler. Assign default value for pointers that are identified by
> > >>>>compiler as non-initialized.
> > >>>
> > >>>s/Right optimize debugging experience is given/
> > >>> Correct debugging experience is given/
> > >
> > >>Right debugging experience is given by passing -Og to compiler.
> > >
> > >So I fixed the spelling here once already :-/ If you want to use
> > >'right' in this context then use it like this:
> > >
> > > The right debugging experience is given by ...
> > >
> > >Or you can use what I suggested first:
> > >
> > > Correct debugging experience is given by ...
> > >
> > >Thanks,
> > >
> > > Ingo
> > >
> >
> > Sorry Ingo for that, I overlooked that correction :)
>
> Are you ok with this Ingo?
Yeah, certainly!
> I can apply, but there seems to be two patches folded here, one that
> sets the possibly unitiliazed variables to NULL, and could be the
> first in the series, and the other, that deals with multiple
> versions of gcc and how should we ask something from them.
Yeah.
Thanks,
Ingo
next prev parent reply other threads:[~2015-05-25 18:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 13:41 [PATCH] perf: fix wrong DEBUG configuration Martin Liška
2015-05-19 14:04 ` Arnaldo Carvalho de Melo
2015-05-20 13:07 ` Martin Liška
2015-05-20 13:17 ` Arnaldo Carvalho de Melo
2015-05-20 13:29 ` Martin Liška
2015-05-20 13:53 ` Arnaldo Carvalho de Melo
2015-05-20 14:55 ` Ingo Molnar
2015-05-20 16:16 ` Martin Liška
2015-05-21 15:05 ` Arnaldo Carvalho de Melo
2015-05-22 7:02 ` Ingo Molnar
2015-05-22 13:50 ` Martin Liška
2015-05-25 8:04 ` Martin Liška
2015-05-25 10:47 ` Ingo Molnar
2015-05-25 11:04 ` Martin Liška
2015-05-25 11:09 ` Ingo Molnar
2015-05-25 11:12 ` Martin Liška
2015-05-25 13:52 ` Arnaldo Carvalho de Melo
2015-05-25 18:32 ` Ingo Molnar [this message]
2015-05-26 9:13 ` Martin Liška
2015-05-26 14:36 ` Arnaldo Carvalho de Melo
2015-05-26 15:22 ` Arnaldo Carvalho de Melo
2015-05-26 15:39 ` Martin Liška
2015-05-26 15:48 ` Martin Liška
2015-05-26 15:53 ` Arnaldo Carvalho de Melo
2015-05-27 16:51 ` [tip:perf/core] perf tools: Assign default value for some pointers tip-bot for Martin Liška
2015-05-27 16:51 ` [tip:perf/core] perf tools: Improve setting of gcc debug option tip-bot for Martin Liska
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=20150525183246.GA21153@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mliska@suse.cz \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).