* Re: [PATCH] perf: delete unused variable tmp to fix new build warning [not found] ` <20140522122142.GA6650@gmail.com> @ 2014-05-22 13:44 ` Paul Gortmaker 2014-05-22 22:10 ` Stephen Rothwell 0 siblings, 1 reply; 2+ messages in thread From: Paul Gortmaker @ 2014-05-22 13:44 UTC (permalink / raw) To: Ingo Molnar Cc: linux-kernel, Peter Zijlstra, Arnaldo Carvalho de Melo, Paul Mackerras, Stephen Rothwell, linux-next@vger.kernel.org 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. ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] perf: delete unused variable tmp to fix new build warning 2014-05-22 13:44 ` [PATCH] perf: delete unused variable tmp to fix new build warning Paul Gortmaker @ 2014-05-22 22:10 ` Stephen Rothwell 0 siblings, 0 replies; 2+ messages in thread From: Stephen Rothwell @ 2014-05-22 22:10 UTC (permalink / raw) To: Paul Gortmaker Cc: Ingo Molnar, linux-kernel, Peter Zijlstra, Arnaldo Carvalho de Melo, Paul Mackerras, linux-next [-- Attachment #1: Type: text/plain, Size: 1090 bytes --] Hi Paul, On Thu, 22 May 2014 09:44:46 -0400 Paul Gortmaker <paul.gortmaker@windriver.com> wrote: > > 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. Ingo and co like to give the tip tree components some pretty good testing before they expose it to linux-next, though usually there is not this long a break between updates. The auto-latest branch has been updated for today's linux-next. -- Cheers, Stephen Rothwell sfr@canb.auug.org.au [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 836 bytes --] ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-05-22 22:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1400700787-11759-1-git-send-email-paul.gortmaker@windriver.com>
[not found] ` <20140522122142.GA6650@gmail.com>
2014-05-22 13:44 ` [PATCH] perf: delete unused variable tmp to fix new build warning Paul Gortmaker
2014-05-22 22:10 ` Stephen Rothwell
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox