All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Borislav Petkov <bp@alien8.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung.kim@lge.com>,
	LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
	David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH] perf tools: Use per-file CFLAGS in Makefile
Date: Fri, 27 Sep 2013 09:38:32 +0900	[thread overview]
Message-ID: <87r4cbp08n.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20130924170842.GA2634@ghostprotocols.net> (Arnaldo Carvalho de Melo's message of "Tue, 24 Sep 2013 14:08:42 -0300")

Hi Arnaldo,

On Tue, 24 Sep 2013 14:08:42 -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Sep 24, 2013 at 05:09:21PM +0900, Namhyung Kim escreveu:
>> I don't know.  I just thought there's not much thing we can do for those
>> files other than shutting up all warnings.
>  
>> But if you think that's not the right thing, I'll keep the existing
>> options.  What do you think, Arnaldo?
>
> I think keeping the existing options is the right thing to do, if some
> of that can be simplified or made like you did it in your patch, then
> that is the matter for a separate patch, with proper explanation.

Okay, I'll just keep them and resend v2.

Thanks,
Namhyung

  reply	other threads:[~2013-09-27  0:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16  2:11 [PATCH] perf tools: Use per-file CFLAGS in Makefile Namhyung Kim
2013-09-20 23:01 ` Borislav Petkov
2013-09-23  9:15   ` Namhyung Kim
2013-09-23  9:26     ` Borislav Petkov
2013-09-24  8:09       ` Namhyung Kim
2013-09-24 17:08         ` Arnaldo Carvalho de Melo
2013-09-27  0:38           ` Namhyung Kim [this message]
2013-09-21 12:47 ` Jiri Olsa
2013-09-23  9:17   ` Namhyung Kim

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=87r4cbp08n.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=bp@alien8.de \
    --cc=dsahern@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung.kim@lge.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.