From: Ingo Molnar <mingo@kernel.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: X86 ML <x86@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
Andrey Skvortsov <andrej.skvortzov@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86/vdso for 3.20
Date: Tue, 3 Feb 2015 12:23:35 +0100 [thread overview]
Message-ID: <20150203112335.GB2511@gmail.com> (raw)
In-Reply-To: <CALCETrWu3nAEcb3ZL31H_uaVjzc-fBC2OLSZ-5Hki=b=FMd8_g@mail.gmail.com>
* Andy Lutomirski <luto@amacapital.net> wrote:
> Hi Ingo and Thomas,
>
> Please consider pulling this trivial fix for tip:x86/vdso.
>
> Thanks,
> Andy
>
> The following changes since commit c59c961ca511dc7ee2f4f7e9c224d16f5c76ca6e:
>
> Merge branch 'drm-fixes' of
> git://people.freedesktop.org/~airlied/linux (2015-01-27 19:12:38
> -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git
> tags/pr-20150201-x86-vdso
>
> for you to fetch changes up to 050835e9d3d6c9bd69cec2b4e67a9eb04ad5fd07:
>
> x86, vdso: teach 'make clean' remove vdso64 binaries (2015-01-28
> 18:44:18 -0800)
>
> ----------------------------------------------------------------
> x86, vdso: One trivial last-minute VDSO build improvement
>
> Andrey noticed that the VDSO build wasn't cleaning itself up. This
> one-liner fixes it.
>
> ----------------------------------------------------------------
> Andrey Skvortsov (1):
> x86, vdso: teach 'make clean' remove vdso64 binaries
>
> arch/x86/vdso/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Pulled into tip:x86/asm, thanks Andy!
Ingo
prev parent reply other threads:[~2015-02-03 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 12:17 [GIT PULL] x86/vdso for 3.20 Andy Lutomirski
2015-02-03 11:23 ` Ingo Molnar [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=20150203112335.GB2511@gmail.com \
--to=mingo@kernel.org \
--cc=andrej.skvortzov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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.