linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@kernel.org>
To: Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Lutomirski <luto@kernel.org>
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86/vdso: Fix asm constraints on vDSO syscall fallbacks
Date: Wed, 3 Oct 2018 16:15:34 -0700	[thread overview]
Message-ID: <CALCETrXMTifqRQjBgXFpQ6kFMYcGirJOYwac8UB1C8RpWmcCqQ@mail.gmail.com> (raw)
In-Reply-To: <tip-715bd9d12f84d8f5cc8ad21d888f9bc304a8eb0b@git.kernel.org>

On Mon, Oct 1, 2018 at 11:30 PM tip-bot for Andy Lutomirski
<tipbot@zytor.com> wrote:
>
> Commit-ID:  715bd9d12f84d8f5cc8ad21d888f9bc304a8eb0b
> Gitweb:     https://git.kernel.org/tip/715bd9d12f84d8f5cc8ad21d888f9bc304a8eb0b
> Author:     Andy Lutomirski <luto@kernel.org>
> AuthorDate: Mon, 1 Oct 2018 12:52:15 -0700
> Committer:  Thomas Gleixner <tglx@linutronix.de>
> CommitDate: Tue, 2 Oct 2018 08:28:15 +0200
>
> x86/vdso: Fix asm constraints on vDSO syscall fallbacks

Ugh, I broke the 32-bit code and failed to test it right.  Incremental
fix coming.

  reply	other threads:[~2018-10-03 23:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01 19:52 [PATCH 0/2] x86/vdso: A bugfix and a selftest Andy Lutomirski
2018-10-01 19:52 ` [PATCH 1/2] x86/vdso: Fix asm constraints on vDSO syscall fallbacks Andy Lutomirski
2018-10-02  6:30   ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2018-10-03 23:15     ` Andy Lutomirski [this message]
2018-10-01 19:52 ` [PATCH 2/2] selftests/x86: Add clock_gettime() tests to test_vdso Andy Lutomirski
2018-10-02  6:31   ` [tip:x86/urgent] " tip-bot for 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=CALCETrXMTifqRQjBgXFpQ6kFMYcGirJOYwac8UB1C8RpWmcCqQ@mail.gmail.com \
    --to=luto@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).