On Tue, Feb 18, 2020 at 12:56:52PM +0000, Marc Zyngier wrote: > I'd really appreciate it if you could send these as a series, instead of > an isolated patch every other day. Same for the non-KVM parts, please :) I *think* the current ones to track are: [PATCH v2] arm64: sdei: Annotate SDEI entry points using new style annotat [PATCH 1/2] arm64: crypto: Modernize some extra assembly annotations [PATCH 2/2] arm64: crypto: Modernize names for AES function macros [PATCH] arm64: entry: Annotate ret_from_fork as code [PATCH] arm64: head: Annotate stext and preserve_boot_args as code [PATCH 1/3] arm64: entry-ftrace.S: Convert to modern annotations for assem [PATCH 2/3] arm64: ftrace: Correct annotation of ftrace_caller assembly [PATCH 3/3] arm64: ftrace: Modernise annotation of return_to_handler [PATCH] arm64: vdso: Convert to modern assembler annotations [PATCH] arm64: vdso32: Convert to modern assembler annotations [PATCH] arm64: entry: Annotate vector table and handlers as code [PATCH] arm64: head.S: Convert to modern annotations for assembly function [PATCH] arm64: kernel: Convert to modern annotations for assembly data [PATCH] arm64: kernel: Convert to modern annotations for assembly function [PATCH] arm64: entry: Additional annotation conversions for entry.S [PATCH v2] arm64: kvm: Annotate assembly using modern annoations [PATCH v6 00/11] arm64: Branch Target Identification support [PATCH] arm64: kvm: Modernize annotation for __bp_harden_hyp_vecs but it's a bit much to follow, especially as there are three trees involved in the above! Will _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
