From: <gregkh@linuxfoundation.org>
To: james.hogan@imgtec.com, gregkh@linuxfoundation.org,
paul.burton@imgtec.com, ralf@linux-mips.org
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "MIPS: Build microMIPS VDSO for microMIPS kernels" has been added to the 4.5-stable tree
Date: Sat, 04 Jun 2016 11:41:06 -0700 [thread overview]
Message-ID: <146506566620328@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
MIPS: Build microMIPS VDSO for microMIPS kernels
to the 4.5-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
mips-build-micromips-vdso-for-micromips-kernels.patch
and it can be found in the queue-4.5 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From bb93078e655be1e24d68f28f2756676e62c037ce Mon Sep 17 00:00:00 2001
From: James Hogan <james.hogan@imgtec.com>
Date: Tue, 24 May 2016 09:35:11 +0100
Subject: MIPS: Build microMIPS VDSO for microMIPS kernels
From: James Hogan <james.hogan@imgtec.com>
commit bb93078e655be1e24d68f28f2756676e62c037ce upstream.
MicroMIPS kernels may be expected to run on microMIPS only cores which
don't support the normal MIPS instruction set, so be sure to pass the
-mmicromips flag through to the VDSO cflags.
Fixes: ebb5e78cc634 ("MIPS: Initial implementation of a VDSO")
Signed-off-by: James Hogan <james.hogan@imgtec.com>
Cc: Paul Burton <paul.burton@imgtec.com>
Cc: linux-mips@linux-mips.org
Patchwork: https://patchwork.linux-mips.org/patch/13349/
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
arch/mips/vdso/Makefile | 1 +
1 file changed, 1 insertion(+)
--- a/arch/mips/vdso/Makefile
+++ b/arch/mips/vdso/Makefile
@@ -5,6 +5,7 @@ obj-vdso-y := elf.o gettimeofday.o sigre
ccflags-vdso := \
$(filter -I%,$(KBUILD_CFLAGS)) \
$(filter -E%,$(KBUILD_CFLAGS)) \
+ $(filter -mmicromips,$(KBUILD_CFLAGS)) \
$(filter -march=%,$(KBUILD_CFLAGS))
cflags-vdso := $(ccflags-vdso) \
$(filter -W%,$(filter-out -Wa$(comma)%,$(KBUILD_CFLAGS))) \
Patches currently in stable-queue which might be from james.hogan@imgtec.com are
queue-4.5/mips64-r6-r2-emulation-bugfix.patch
queue-4.5/mips-fix-uapi-include-in-exported-asm-siginfo.h.patch
queue-4.5/mips-disable-preemption-during-prctl-pr_set_fp_mode.patch
queue-4.5/mips-fix-sigreturn-via-vdso-on-micromips-kernel.patch
queue-4.5/mips-fix-siginfo.h-to-use-strict-posix-types.patch
queue-4.5/mips-don-t-unwind-to-user-mode-with-eva.patch
queue-4.5/mips-vdso-build-with-fno-strict-aliasing.patch
queue-4.5/mips-fix-watchpoint-restoration.patch
queue-4.5/mips-build-micromips-vdso-for-micromips-kernels.patch
queue-4.5/mips-math-emu-fix-jalr-emulation-when-rd-0.patch
queue-4.5/mips-fix-msa-ld_-st_-asm-macros-to-use-ptr_addu.patch
queue-4.5/mips-avoid-using-unwind_stack-with-usermode.patch
queue-4.5/mips-prevent-restoration-of-msa-context-in-non-msa-kernels.patch
queue-4.5/mips-use-copy_s.fmt-rather-than-copy_u.fmt.patch
reply other threads:[~2016-06-04 18:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=146506566620328@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=james.hogan@imgtec.com \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=stable-commits@vger.kernel.org \
--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 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.