linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Martin Liška" <mliska@suse.cz>
Cc: Ingo Molnar <mingo@kernel.org>,
	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: Tue, 26 May 2015 12:22:00 -0300	[thread overview]
Message-ID: <20150526152200.GI17970@kernel.org> (raw)
In-Reply-To: <20150526143626.GH17970@kernel.org>

Em Tue, May 26, 2015 at 11:36:26AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Tue, May 26, 2015 at 11:13:32AM +0200, Martin Liška escreveu:
> > As Arnaldo pointed, I split the patch to following 2 smaller patches.
> 
> Thanks, but how did you generated the two attached patches? 
> 
>  [acme@ssdandy linux]$ git am /wb/0001-perf-Fix-compiler-warnings.patch 
>   Patch format detection failed.
> 
> So I'll fix it up manually, next time please try:
> 
>   git format-patch -n HEAD^^..
> 
> Or equivalent,

I am also splitting the second patch into two, as it does two unrelated
things:

1. Conditionally use -Og instead of -O0 

2. Use -O3 instead of -O6, as -O6 is the same as -O3 currently

And I am not applying the second, as it doesn't fixes anything nor
improves the current situation, right?

- Arnaldo

  reply	other threads:[~2015-05-26 15:22 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
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 [this message]
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=20150526152200.GI17970@kernel.org \
    --to=acme@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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).