linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H . Peter Anvin" <hpa@zytor.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
	Jason Andryuk <jandryuk@gmail.com>,
	Laszlo Ersek <lersek@redhat.com>, "Lee, Chun-Yi" <jlee@suse.com>,
	Matthew Garrett <mjg59@coreos.com>,
	Peter Jones <pjones@redhat.com>
Subject: [GIT PULL 0/2] EFI urgent fixes
Date: Tue, 16 Feb 2016 12:59:18 +0000	[thread overview]
Message-ID: <1455627560-10576-1-git-send-email-matt@codeblueprint.co.uk> (raw)

Folks, here are some bug fixes that missed the previous pull request
but that are related to those patches.

The following changes since commit 4682c211a80ee93214b72d95f861b0f6e90e5445:

  Merge tag 'efi-urgent' of git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi into x86/urgent (2016-02-16 13:14:57 +0100)

are available in the git repository at:

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

for you to fetch changes up to a68075908a37850918ad96b056acc9ac4ce1bd90:

  lib/ucs2_string: Correct ucs2 -> utf8 conversion (2016-02-16 12:49:05 +0000)

----------------------------------------------------------------
 * Fix bugs in our code that converts ucs2 strings to utf8 where we
   unintentionally drop bits from the original string - Jason Andryuk

 * Add the efi-pstore variables to the variable whitelist so that
   users can continue to delete them via efivarfs without needing to
   manipulate the immutable flag - Matt Fleming

----------------------------------------------------------------
Jason Andryuk (1):
      lib/ucs2_string: Correct ucs2 -> utf8 conversion

Matt Fleming (1):
      efi: Add pstore variables to the deletion whitelist

 drivers/firmware/efi/vars.c |  1 +
 lib/ucs2_string.c           | 14 +++++++-------
 2 files changed, 8 insertions(+), 7 deletions(-)

             reply	other threads:[~2016-02-16 12:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 12:59 Matt Fleming [this message]
2016-02-16 12:59 ` [PATCH 1/2] efi: Add pstore variables to the deletion whitelist Matt Fleming
2016-02-16 12:59 ` [PATCH 2/2] lib/ucs2_string: Correct ucs2 -> utf8 conversion Matt Fleming
2016-02-16 15:47 ` [GIT PULL 0/2] EFI urgent fixes Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2016-11-12 21:04 Matt Fleming
2016-09-20 14:48 Matt Fleming
2016-09-20 14:58 ` Ingo Molnar
2016-09-20 15:20 ` Waiman Long
     [not found]   ` <57E153B1.3040907-ZPxbGqLxI0U@public.gmane.org>
2016-09-20 15:27     ` Matt Fleming
2016-08-11 10:41 Matt Fleming
2016-05-31 10:23 Matt Fleming
     [not found] ` <1464690224-4503-1-git-send-email-matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-06-06 10:02   ` Matt Fleming
2016-06-08  7:24     ` Ingo Molnar
2015-09-25 22:02 Matt Fleming

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=1455627560-10576-1-git-send-email-matt@codeblueprint.co.uk \
    --to=matt@codeblueprint.co.uk \
    --cc=ard.biesheuvel@linaro.org \
    --cc=hpa@zytor.com \
    --cc=jandryuk@gmail.com \
    --cc=jlee@suse.com \
    --cc=lersek@redhat.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mjg59@coreos.com \
    --cc=pjones@redhat.com \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).