From: Nick Desaulniers <ndesaulniers@google.com>
To: Will Deacon <will@kernel.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH v5 2/6] arm64: vdso32: Detect binutils support for dmb ishld
Date: Thu, 3 Oct 2019 13:56:39 -0700 [thread overview]
Message-ID: <CAKwvOdm4ccfhXDDSKXgdN4qkn2NHwAHKCwRV7OqLEG_PQj09vQ@mail.gmail.com> (raw)
In-Reply-To: <20191003204944.6wuzflqkjdpawzvp@willie-the-truck>
On Thu, Oct 3, 2019 at 1:49 PM Will Deacon <will@kernel.org> wrote:
>
> On Thu, Oct 03, 2019 at 01:18:16PM -0700, Nick Desaulniers wrote:
> > On Thu, Oct 3, 2019 at 10:48 AM Vincenzo Frascino
> > <vincenzo.frascino@arm.com> wrote:
> > >
> > > Older versions of binutils that do not support certain types of memory
> > > barriers can cause build failure of the vdso32 library.
> >
> > Do you know specific version numbers of binutils that are affected?
> > May be helpful to have in the commit message just for future
> > travelers.
>
> A quick bit of archaeology suggests e797f7e0b2be added this back in 2012,
> which seems to correlate with the 2.24 release.
Cool, thanks for digging. Vincenzo, can we please add that to the
commit message?
--
Thanks,
~Nick Desaulniers
next prev parent reply other threads:[~2019-10-03 20:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 17:48 [PATCH v5 0/6] arm64: vdso32: Address various issues Vincenzo Frascino
2019-10-03 17:48 ` [PATCH v5 1/6] arm64: vdso32: Fix syncconfig errors Vincenzo Frascino
2019-10-03 17:48 ` [PATCH v5 2/6] arm64: vdso32: Detect binutils support for dmb ishld Vincenzo Frascino
2019-10-03 20:18 ` Nick Desaulniers
2019-10-03 20:49 ` Will Deacon
2019-10-03 20:56 ` Nick Desaulniers [this message]
2019-10-03 20:59 ` Will Deacon
2019-10-03 21:50 ` Nick Desaulniers
2019-10-03 17:48 ` [PATCH v5 3/6] arm64: Remove gettimeofday.S Vincenzo Frascino
2019-10-03 17:48 ` [PATCH v5 4/6] arm64: vdso32: Remove jump label config option in Makefile Vincenzo Frascino
2019-10-03 17:48 ` [PATCH v5 5/6] arm64: Remove vdso_datapage.h Vincenzo Frascino
2019-10-03 17:48 ` [PATCH v5 6/6] lib: vdso: Remove CROSS_COMPILE_COMPAT_VDSO Vincenzo Frascino
2019-10-07 13:31 ` [PATCH v5 0/6] arm64: vdso32: Address various issues Will Deacon
2019-10-07 13:54 ` Vincenzo Frascino
2019-10-07 14:15 ` Will Deacon
2019-10-07 14:37 ` Vincenzo Frascino
2019-10-07 17:48 ` Vincenzo Frascino
2019-10-08 9:07 ` 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=CAKwvOdm4ccfhXDDSKXgdN4qkn2NHwAHKCwRV7OqLEG_PQj09vQ@mail.gmail.com \
--to=ndesaulniers@google.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@arm.com \
--cc=will@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 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).