linux-kernel - [GIT PULL] EFI changes

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-next>] [day] [month] [year] [list]

Message-ID: <20131004195550.GA21783@console-pimps.org>
Date:	Fri, 4 Oct 2013 20:55:50 +0100
From:	Matt Fleming <matt@...sole-pimps.org>
To:	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...nel.org>
Cc:	linux-efi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [GIT PULL] EFI changes

These changes fix a couple of sparse warnings introduced in the last
pull.

The following changes since commit 0ce6cda2c75d64175394341ef60e6e1d27dd9c10:

  x86 efi: bugfix interrupt disabling sequence (2013-09-30 10:23:11 +0100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-next

for you to fetch changes up to c158c3bf59951bbb44bd7ccca9e6665dfd1617c5:

  boot, efi: Remove redundant memset() (2013-10-04 20:07:47 +0100)

----------------------------------------------------------------
 * Fix a recently introduced sparse warning caused by using 0 instead of
   NULL - Leif Lindholm

 * Remove a useless memset from the common EFI stub code - Roy Franz

----------------------------------------------------------------
Leif Lindholm (1):
      x86/efi: Fix config_table_type array termination

Roy Franz (1):
      boot, efi: Remove redundant memset()

 arch/x86/platform/efi/efi.c            | 2 +-
 drivers/firmware/efi/efi-stub-helper.c | 2 --
 2 files changed, 1 insertion(+), 3 deletions(-)

-- 
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/