From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/12] arm+arm64: vdso unification to lib/vdso/
Date: Tue, 31 Oct 2017 09:49:53 +0000 [thread overview]
Message-ID: <20171031094953.GA5584@arm.com> (raw)
In-Reply-To: <20171030214434.ta26ekbg7jyws2lf@salmiak>
On Mon, Oct 30, 2017 at 09:44:35PM +0000, Mark Rutland wrote:
> On Mon, Oct 30, 2017 at 01:34:13PM -0700, Mark Salyzyn wrote:
> > On 10/30/2017 07:18 AM, Mark Rutland wrote:
> > > On Fri, Oct 27, 2017 at 03:23:48PM -0700, Mark Salyzyn wrote:
> > > > Note I noticed a bug in the old implementation of __kernel_clock_getres;
> > > > it was checking only the lower 32bits of the pointer; this would work
> > > > for most cases but could fail in a few.
> > > Sorry if this is a stupid question, but do you mean from a prior version
> > > of this series, or the one in the kernel today?
> >
> > apinski at cavium.com noticed this as part of the existing upstream arm64
> > assembler when he did the original conversion to C.
>
> Just to check, does the below address the issue, or is there something that
> I've missed?
Looks fine to me. Applied.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Mark Salyzyn <salyzyn@android.com>,
linux-kernel@vger.kernel.org, James Morse <james.morse@arm.com>,
Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Andy Lutomirski <luto@amacapital.net>,
Dmitry Safonov <dsafonov@virtuozzo.com>,
John Stultz <john.stultz@linaro.org>,
Laura Abbott <labbott@redhat.com>,
Kees Cook <keescook@chromium.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Andy Gross <andy.gross@linaro.org>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Andrew Pinski <apinski@cavium.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/12] arm+arm64: vdso unification to lib/vdso/
Date: Tue, 31 Oct 2017 09:49:53 +0000 [thread overview]
Message-ID: <20171031094953.GA5584@arm.com> (raw)
In-Reply-To: <20171030214434.ta26ekbg7jyws2lf@salmiak>
On Mon, Oct 30, 2017 at 09:44:35PM +0000, Mark Rutland wrote:
> On Mon, Oct 30, 2017 at 01:34:13PM -0700, Mark Salyzyn wrote:
> > On 10/30/2017 07:18 AM, Mark Rutland wrote:
> > > On Fri, Oct 27, 2017 at 03:23:48PM -0700, Mark Salyzyn wrote:
> > > > Note I noticed a bug in the old implementation of __kernel_clock_getres;
> > > > it was checking only the lower 32bits of the pointer; this would work
> > > > for most cases but could fail in a few.
> > > Sorry if this is a stupid question, but do you mean from a prior version
> > > of this series, or the one in the kernel today?
> >
> > apinski@cavium.com noticed this as part of the existing upstream arm64
> > assembler when he did the original conversion to C.
>
> Just to check, does the below address the issue, or is there something that
> I've missed?
Looks fine to me. Applied.
Will
next prev parent reply other threads:[~2017-10-31 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 22:23 [PATCH v3 0/12] arm+arm64: vdso unification to lib/vdso/ Mark Salyzyn
2017-10-27 22:23 ` Mark Salyzyn
2017-10-30 14:18 ` Mark Rutland
2017-10-30 14:18 ` Mark Rutland
2017-10-30 20:34 ` Mark Salyzyn
2017-10-30 20:34 ` Mark Salyzyn
2017-10-30 21:44 ` Mark Rutland
2017-10-30 21:44 ` Mark Rutland
2017-10-31 9:49 ` Will Deacon [this message]
2017-10-31 9:49 ` Will Deacon
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=20171031094953.GA5584@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.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 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.