All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ben Hutchings <ben@decadent.org.uk>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH perf 0/4] Build fixes for gcc 6
Date: Tue, 19 Jan 2016 23:43:17 +0100	[thread overview]
Message-ID: <20160119224317.GG321@x4> (raw)
In-Reply-To: <20160119223018.GN27085@kernel.org>

On 2016.01.19 at 19:30 -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jan 19, 2016 at 07:28:51PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Tue, Jan 19, 2016 at 11:00:50PM +0100, Markus Trippelsdorf escreveu:
> > > On 2016.01.19 at 21:58 +0000, Ben Hutchings wrote:
> > > > On Tue, Jan 19, 2016 at 10:40:18PM +0100, Markus Trippelsdorf wrote:
> > > > > On 2016.01.19 at 21:32 +0000, Ben Hutchings wrote:
> > > > > > gcc 6 warns about various things in tools/perf  and with -Werror
> > > > > > these turn into build failures.  One of them is a real though not
> > > > > > very serious bug.
> > > > > 
> > > > > I've already send patches for 1,2 and 4. See:
> > > > > https://lkml.org/lkml/2015/12/14/460
> > > > > 
> > > > > Not sure what happened with them. Also your patch number 4 is wrong, you
> > > > > should just delete the semicolon.
> > > > 
> > > > I think that the busy-wait, intentional or not, may be a necessary
> > > > part of the test case.
> > > 
> > > Well, the author of the code thinks otherwise:
> > > 
> > > https://lkml.org/lkml/2015/12/14/269
> > 
> > Right, I saw those and I think I haven't processed them because I was
> > waiting for those to be broken up in separate patches after I read
> > Ingo's comment about one of them fixing up a real bug, a part that the
> > original autor, mfleming even acked, could you please break it down into
> > multiple patches?
> 
> Alternatively I can do it for the patch acked by Matt and use the other
> patches from Ben, that even have the Fixes: tags (yay, those are
> appreciated!).

Just use what is easiest for you to work with. I don't really mind.

-- 
Markus

  reply	other threads:[~2016-01-19 22:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 21:32 [PATCH perf 0/4] Build fixes for gcc 6 Ben Hutchings
2016-01-19 21:32 ` [PATCH perf 1/4] perf tools: Fix wrong indentation and build failure with " Ben Hutchings
2016-01-19 21:32 ` [PATCH perf 2/4] perf top: Fix behaviour of Shift-Tab in annotated view with nothing focussed Ben Hutchings
2016-01-19 21:33 ` [PATCH perf 3/4] perf tools: Fix unused variables: x86_{32,64}_regoffset_table Ben Hutchings
2016-01-20 13:59   ` Arnaldo Carvalho de Melo
2016-01-21  4:43     ` Wangnan (F)
2016-01-21 15:38       ` Arnaldo Carvalho de Melo
2016-01-21 15:41         ` Arnaldo Carvalho de Melo
2016-01-22  1:26           ` Wangnan (F)
2016-01-22  5:56       ` 平松雅巳 / HIRAMATU,MASAMI
2016-01-22  6:19         ` Wangnan (F)
2016-01-22  7:59           ` 平松雅巳 / HIRAMATU,MASAMI
2016-01-19 21:33 ` [PATCH perf 4/4] perf tests: Delete mis-indented dead code that causes build failure with gcc 6 Ben Hutchings
2016-01-19 21:40 ` [PATCH perf 0/4] Build fixes for " Markus Trippelsdorf
2016-01-19 21:58   ` Ben Hutchings
2016-01-19 22:00     ` Markus Trippelsdorf
2016-01-19 22:04       ` Ben Hutchings
2016-01-19 22:28       ` Arnaldo Carvalho de Melo
2016-01-19 22:30         ` Arnaldo Carvalho de Melo
2016-01-19 22:43           ` Markus Trippelsdorf [this message]
2016-01-19 22:31         ` Markus Trippelsdorf
2016-01-20 13:20           ` Arnaldo Carvalho de Melo

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=20160119224317.GG321@x4 \
    --to=markus@trippelsdorf.de \
    --cc=acme@kernel.org \
    --cc=ben@decadent.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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.