linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
	linux-efi <linux-efi@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>, stable <stable@vger.kernel.org>
Subject: Re: [PATCH 2/2] efi: efi_guid_t must be 64-bit aligned
Date: Wed, 19 Dec 2018 09:06:37 -0500	[thread overview]
Message-ID: <20181219140637.GL2746@sasha-vm> (raw)
In-Reply-To: <CAKv+Gu8AZ6MemE5Z90L5nvrj51z3=rJ_tF=7Wknzs0_RKk_iOQ@mail.gmail.com>

On Wed, Dec 19, 2018 at 11:07:53AM +0100, Ard Biesheuvel wrote:
>On Tue, 18 Dec 2018 at 21:41, Sasha Levin <sashal@kernel.org> wrote:
>>
>> Hi,
>>
>> [This is an automated email]
>>
>> This commit has been processed because it contains a -stable tag.
>> The stable tag indicates that it's relevant for the following trees: all
>>
>> The bot has tested the following trees: v4.19.10, v4.14.89, v4.9.146, v4.4.168, v3.18.130,
>>
>
>Please disregard this patch for -stable until we decide how we are
>going to fix the 32-bit array packing issue.

No worries, we won't take any patches until they are actually upstream.
These mails just help us get more responses with regards to how
backports should be done.

      reply	other threads:[~2018-12-19 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 18:02 [GIT PULL 0/2] Final EFI fixes for v4.20 Ard Biesheuvel
2018-12-17 18:02 ` [PATCH 1/2] efi: let kmemleak ignore false positives Ard Biesheuvel
2018-12-17 18:02 ` [PATCH 2/2] efi: efi_guid_t must be 64-bit aligned Ard Biesheuvel
     [not found]   ` <20181218204116.6D58A2184C@mail.kernel.org>
2018-12-19 10:07     ` Ard Biesheuvel
2018-12-19 14:06       ` Sasha Levin [this message]

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=20181219140637.GL2746@sasha-vm \
    --to=sashal@kernel.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=xypron.glpk@gmx.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).