linux-kernel - Re: [PATCH V5 00/18] ARM EFI stub common code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Sep 2013 13:11:20 +0100
From:	Matt Fleming <matt@...sole-pimps.org>
To:	Roy Franz <roy.franz@...aro.org>
Cc:	linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org,
	matt.fleming@...el.com, leif.lindholm@...aro.org,
	grant.likely@...aro.org, msalter@...hat.com
Subject: Re: [PATCH V5 00/18] ARM EFI stub common code

On Sun, 22 Sep, at 03:45:24PM, Roy Franz wrote:
> This patch is the common/x86 portion of the ARM EFI stub
> patchset broken out.  These changes support the addition
> of EFI stub support for the ARM and ARM64 architectures.
> The common code that is now shared in efi-stub-helper.c
> is based on code in the x86 stub that has been generalized
> to support other architectures.

OK, I've applied this patch series (excluding PATCH 10) to the
'arm/common' branch in the EFI repository at,

  git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git

At the request of Grant, the patches series from both Roy and Leif are
available in a clean branch with a linear history at 'efi-arm', which is
based on v3.11. Grant, feel free to pull that branch into wherever it is
required. If this layout doesn't work for you guys then just shout and
we can come up with a scheme that does.

I'm going to send a pull request for the 'next' branch to the tip folks,
so that these patches can get some testing via linux-next.

-- 
Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/