From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64 fix for -rc7
Date: Fri, 24 Jul 2020 12:52:36 +0100 [thread overview]
Message-ID: <20200724115236.GB17451@willie-the-truck> (raw)
Hi Linus,
Please pull this tiny arm64 fix for -rc7, which tells recent versions of
clang where to find the assembler for building the compat vDSO.
Cheers,
Will
--->8
The following changes since commit f32ed8eb0e3f0d0ef4ddb854554d60ca5863a9f9:
drivers/perf: Prevent forced unbinding of PMU drivers (2020-07-17 10:51:44 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes
for you to fetch changes up to 7b7891c7bdfd61fc9ed6747a0a05efe2394dddc6:
arm64: vdso32: Fix '--prefix=' value for newer versions of clang (2020-07-23 10:57:32 +0100)
----------------------------------------------------------------
arm64 fix for -rc7
- Fix compat vDSO build flags for recent versions of clang
----------------------------------------------------------------
Nathan Chancellor (1):
arm64: vdso32: Fix '--prefix=' value for newer versions of clang
arch/arm64/kernel/vdso32/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-07-24 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 11:52 Will Deacon [this message]
2020-07-24 21:40 ` [GIT PULL] arm64 fix for -rc7 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-11-08 10:32 [GIT PULL] arm64: Fix " Will Deacon
2019-11-08 17:55 ` pr-tracker-bot
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=20200724115236.GB17451@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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