From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Paul Mackerras <paulus@samba.org>,
linux-next@vger.kernel.org
Subject: Re: [PATCH] perf: delete unused variable tmp to fix new build warning
Date: Fri, 23 May 2014 08:10:52 +1000 [thread overview]
Message-ID: <20140523081052.51ffeb1b@canb.auug.org.au> (raw)
In-Reply-To: <537DFF4E.4070503@windriver.com>
[-- 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 --]
prev parent reply other threads:[~2014-05-22 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 message]
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=20140523081052.51ffeb1b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=paulus@samba.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox