From: Andrey Skvortsov <andrej.skvortzov@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "H. Peter Anvin" <hpa@zytor.com>, X86 ML <x86@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] x86, vdso: teach 'make clean' remove generated vdso-image-*.c files
Date: Mon, 16 Mar 2015 21:23:28 +0300 [thread overview]
Message-ID: <20150316182328.GA1808@nest> (raw)
In-Reply-To: <CALCETrVC7d4irG0wOm8-POD2xaXytWDsM8zwVi55dcupZT=yMw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
On 16 Mar, Andy Lutomirski wrote:
> On Mar 16, 2015 8:23 AM, "Andrey Skvortsov" <andrej.skvortzov@gmail.com> wrote:
> >
> > After 'make clean' vdso-image-32-int80.c vdso-image-32-syscall.c
> > vdso-image-32-sysenter.c were left in arch/x86/vdso.
> > These file are generated during build process and present in .gitignore.
>
> This issue is fixed slightly differently here:
>
> https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/commit/?h=x86/vdso
>
> I'll send out the pull request soon -- I'm just waiting on some KVM
> stuff to help decide exactly what ends up in the pull request.
Ok. No problem.
--
Best regards,
Andrey Skvortsov
Secure e-mail with gnupg: See http://www.gnupg.org/
PGP Key ID: 0x57A3AEAD
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-16 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 15:23 [PATCH] x86, vdso: teach 'make clean' remove generated vdso-image-*.c files Andrey Skvortsov
2015-03-16 15:33 ` Andy Lutomirski
2015-03-16 18:23 ` Andrey Skvortsov [this message]
2015-03-26 0:52 ` Andy Lutomirski
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=20150316182328.GA1808@nest \
--to=andrej.skvortzov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--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.