All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: [PATCH] perf: delete unused variable tmp to fix new build warning
Date: Thu, 22 May 2014 09:44:46 -0400	[thread overview]
Message-ID: <537DFF4E.4070503@windriver.com> (raw)
In-Reply-To: <20140522122142.GA6650@gmail.com>

On 14-05-22 08:21 AM, Ingo Molnar wrote:
> 
> * Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> 
>> commit 3a497f48637e2aac17eabb84a17f8ac5216028fc [tip:perf/core]
>> ("perf: Simplify perf_event_exit_task_context()") deleted the
>> code that was using tmp but not the declaration of it, causing:
>>
>> kernel/events/core.c:7434:35: warning: unused variable ‘tmp’ [-Wunused-variable]
> 
> This warning should be addressed by:
> 
>   12665b35b0b4 perf/events/core: Drop unused variable after cleanup

Indeed - and I now see that commit when I switch over to my tip repo.

However 12665b35b0b4 is not present in linux-next of yesterday or today
(21/22) for some reason.  The tip/auto-latest merged into next has this:

commit 1974363f7e899dc1b9e6e774dc885c7980a7159b
Merge: 67367e2c3f76 7fd44dacdd80
Author: Ingo Molnar <mingo@kernel.org>
Date:   Thu May 8 12:40:28 2014 +0200

    Merge branch 'x86/x32'

as its top commit.  Today's auto-latest in tip shows a similar merge, but
with today's date (and it contains Boris' warning fix too.)  Adding Stephen
to CC in case it is something related to linux-next infrastructure.

Thanks,
Paul.

WARNING: multiple messages have this Message-ID (diff)
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: [PATCH] perf: delete unused variable tmp to fix new build warning
Date: Thu, 22 May 2014 09:44:46 -0400	[thread overview]
Message-ID: <537DFF4E.4070503@windriver.com> (raw)
In-Reply-To: <20140522122142.GA6650@gmail.com>

On 14-05-22 08:21 AM, Ingo Molnar wrote:
> 
> * Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> 
>> commit 3a497f48637e2aac17eabb84a17f8ac5216028fc [tip:perf/core]
>> ("perf: Simplify perf_event_exit_task_context()") deleted the
>> code that was using tmp but not the declaration of it, causing:
>>
>> kernel/events/core.c:7434:35: warning: unused variable ‘tmp’ [-Wunused-variable]
> 
> This warning should be addressed by:
> 
>   12665b35b0b4 perf/events/core: Drop unused variable after cleanup

Indeed - and I now see that commit when I switch over to my tip repo.

However 12665b35b0b4 is not present in linux-next of yesterday or today
(21/22) for some reason.  The tip/auto-latest merged into next has this:

commit 1974363f7e899dc1b9e6e774dc885c7980a7159b
Merge: 67367e2c3f76 7fd44dacdd80
Author: Ingo Molnar <mingo@kernel.org>
Date:   Thu May 8 12:40:28 2014 +0200

    Merge branch 'x86/x32'

as its top commit.  Today's auto-latest in tip shows a similar merge, but
with today's date (and it contains Boris' warning fix too.)  Adding Stephen
to CC in case it is something related to linux-next infrastructure.

Thanks,
Paul.

  reply	other threads:[~2014-05-22 13:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 19:33 [PATCH] perf: delete unused variable tmp to fix new build warning Paul Gortmaker
2014-05-22 12:21 ` Ingo Molnar
2014-05-22 13:44   ` Paul Gortmaker [this message]
2014-05-22 13:44     ` Paul Gortmaker
2014-05-22 22:10     ` Stephen Rothwell
2014-05-22 22:10       ` Stephen Rothwell

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=537DFF4E.4070503@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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.