From: Nathan Lynch <Nathan_Lynch@mentor.com>
To: Alexander Kochetkov <al.kochet@gmail.com>
Cc: <stable@vger.kernel.org>, Russell King <rmk+kernel@arm.linux.org.uk>
Subject: Re: [PATCH 1/3] ARM: 8385/1: VDSO: group link options
Date: Wed, 19 Aug 2015 16:05:42 -0500 [thread overview]
Message-ID: <55D4EFA6.3010701@mentor.com> (raw)
In-Reply-To: <1439598757-5029-2-git-send-email-al.kochet@gmail.com>
On 08/14/2015 07:32 PM, Alexander Kochetkov wrote:
> From: Nathan Lynch <nathan_lynch@mentor.com>
>
> commit d33ce23b2160d26b27a47092da5d556b5b11a12a upstream.
>
> Currently the VDSO's link options are kind of a mess spread between
>
> ccflags-y and cmd_vdsold. Collect linker directives into one
> variable, VDSO_LDFLAGS, and use that in cmd_vdsold.
>
> Signed-off-by: Nathan Lynch <nathan_lynch@mentor.com>
> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Since they fix a build regression with certain toolchains[*], I agree
with putting the ARM VDSO patches (#1 and #2 from this thread) into
4.1-stable, as long as 3473f26592c1c "ARM: 8405/1: VDSO: fix regression
with toolchains lacking ld.bfd executable" is applied immediately
afterward, since it fixes a problem introduced by #2.
[*] Toolchains built by the Angstrom distribution from Linaro sources,
not current binary toolchains as distributed by Linaro, as implied in
the cover letter. One change Angstrom makes is the choice of default
linker, which is what exposed the problem in the first place.
next prev parent reply other threads:[~2015-08-19 21:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 0:32 [PATCH 0/3] Patches to apply to v4.1-stable Alexander Kochetkov
2015-08-15 0:32 ` [PATCH 1/3] ARM: 8385/1: VDSO: group link options Alexander Kochetkov
2015-08-19 21:05 ` Nathan Lynch [this message]
2015-08-15 0:32 ` [PATCH 2/3] ARM: 8384/1: VDSO: force use of BFD linker Alexander Kochetkov
2015-08-15 0:32 ` [PATCH 3/3] ARM: v7 setup function should invalidate L1 cache Alexander Kochetkov
2015-08-15 8:00 ` Russell King - ARM Linux
2015-08-15 10:50 ` Alexander Kochetkov
2015-08-15 10:50 ` [PATCH] ARM: invalidate L1 before enabling coherency Alexander Kochetkov
2015-09-11 6:11 ` [PATCH 0/3] Patches to apply to v4.1-stable Greg KH
2015-09-12 11:59 ` Alexander Kochetkov
2015-09-12 15:51 ` Greg KH
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=55D4EFA6.3010701@mentor.com \
--to=nathan_lynch@mentor.com \
--cc=al.kochet@gmail.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=stable@vger.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).