From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 00/14] EFI capsule update support for IOT2000 devices
Date: Fri, 15 Sep 2017 14:51:13 +0100 [thread overview]
Message-ID: <1505483473.1860.6.camel@codethink.co.uk> (raw)
In-Reply-To: <8ec2546d-9421-5c72-3e55-f4d4586338e2@siemens.com>
On Thu, 2017-09-14 at 21:39 +0200, Jan Kiszka wrote:
> On 2017-09-14 20:42, Ben Hutchings wrote:
> > On Wed, 2017-08-30 at 21:13 +0200, Jan Kiszka wrote:
> >> Last chunk: This backports EFI capsule updates, primarily for the use
> >> with the IOT2020 and IOT2040, the latter with Quark-proprietary security
> >> header format. The feature should also work for the Galileo Gen 2 and,
> >> at least conceptually, for any EFI capsule update compatible firmware.
> > [...]
> >
> > Applied these, but shouldn't I also apply:
> >
> > commit 62075e581802ea1842d5d3c490a7e46330bdb9e1
> > Author: Matt Fleming <matt@codeblueprint.co.uk>
> > Date: Fri May 6 22:39:27 2016 +0100
> >
> > efi/capsule: Make efi_capsule_pending() lockless
> >
>
> Indeed - I should have read more than the subject line (which sounded
> like optimization).
>
> Please add to the queue.
OK, will do.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
prev parent reply other threads:[~2017-09-15 13:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 19:13 [cip-dev] [PATCH 00/14] EFI capsule update support for IOT2000 devices Jan Kiszka
2017-08-30 19:13 ` [cip-dev] [PATCH 01/14] efi: Move efi_status_to_err() to drivers/firmware/efi/ Jan Kiszka
2017-08-30 19:13 ` [cip-dev] [PATCH 02/14] efi: Add 'capsule' update support Jan Kiszka
2017-08-30 19:13 ` [cip-dev] [PATCH 03/14] x86/efi: Force EFI reboot to process pending capsules Jan Kiszka
2017-08-30 19:13 ` [cip-dev] [PATCH 04/14] efi: Add misc char driver interface to update EFI firmware Jan Kiszka
2017-08-30 19:13 ` [cip-dev] [PATCH 05/14] efi/capsule: Move 'capsule' to the stack in efi_capsule_supported() Jan Kiszka
2017-08-30 19:13 ` [cip-dev] [PATCH 06/14] efi/capsule: Allocate whole capsule into virtual memory Jan Kiszka
2017-08-30 19:13 ` [cip-dev] [PATCH 07/14] efi/capsule: Fix return code on failing kmap/vmap Jan Kiszka
2017-08-30 19:13 ` [cip-dev] [PATCH 08/14] efi/capsule: Remove pr_debug() on ENOMEM or EFAULT Jan Kiszka
2017-08-30 19:13 ` [cip-dev] [PATCH 09/14] efi/capsule: Clean up pr_err/_info() messages Jan Kiszka
2017-08-30 19:13 ` [cip-dev] [PATCH 10/14] efi/capsule: Adjust return type of efi_capsule_setup_info() Jan Kiszka
2017-08-30 19:13 ` [cip-dev] [PATCH 11/14] efi/capsule-loader: Use a cached copy of the capsule header Jan Kiszka
2017-08-30 19:13 ` [cip-dev] [PATCH 12/14] efi/capsule-loader: Redirect calls to efi_capsule_setup_info() via weak alias Jan Kiszka
2017-08-30 19:13 ` [cip-dev] [PATCH 13/14] efi/capsule-loader: Use page addresses rather than struct page pointers Jan Kiszka
2017-08-30 19:13 ` [cip-dev] [PATCH 14/14] efi/capsule: Add support for Quark security header Jan Kiszka
2017-08-30 19:24 ` [cip-dev] [PATCH 00/14] EFI capsule update support for IOT2000 devices Ard Biesheuvel
2017-08-30 19:27 ` Jan Kiszka
2017-08-30 19:31 ` Ard Biesheuvel
2017-09-14 18:42 ` Ben Hutchings
2017-09-14 19:39 ` Jan Kiszka
2017-09-15 13:51 ` Ben Hutchings [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=1505483473.1860.6.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/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