public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-efi@vger.kernel.org, Aaron Ma <aaron.ma@canonical.com>,
	Alistair Strachan <astrachan@google.com>,
	Ben Hutchings <ben@decadent.org.uk>,
	Bhupesh Sharma <bhsharma@redhat.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Ivan Hu <ivan.hu@canonical.com>,
	Jeremy Linton <jeremy.linton@arm.com>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	Peter Robinson <pbrobinson@redhat.com>,
	Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Stefan Agner <stefan@agner.ch>
Subject: Re: [GIT PULL 00/11] EFI updates for v4.20
Date: Tue, 2 Oct 2018 10:38:17 +0200	[thread overview]
Message-ID: <20181002083817.GC120270@gmail.com> (raw)
In-Reply-To: <20181002083456.GB120270@gmail.com>


* Ingo Molnar <mingo@kernel.org> wrote:

> 
> * Marc Zyngier <marc.zyngier@arm.com> wrote:
> 
> > Hi all,
> > 
> > On 27/09/18 09:50, Ard Biesheuvel wrote:
> > > Thomas, Ingo,
> > > 
> > > Please pull/cherry-pick the below. Note that the first three patches will
> > > be depended upon by an irqchip series that Marc Zyngier has sent out last
> > > week, and that targets the next release as well. So please advise how to
> > > proceed with that: we could simply apply those patches first and use the
> > > resulting commit in tip.git as a stable branch, I suppose, but I'll let
> > > Marc chime in in case he has any other ideas.
> > 
> > A stable branch with these three patches would be great. The irqchip code
> > will also end-up in tip, so it should all be quite easy to manage anyway.
> 
> Yeah - nevertheless, to keep it all separated nicely, I've created a new
> topic tree for this: tip:efi/irqchip (2e3ac98133a3), with just these three
> patches on top of latest -git.
> 
> That way it can then all be iterated separately.
> 
> Does this approach work for you?

It's a23d3bb05ccb - i.e. the commit ID of Ard's tree, so if you already based your work on top 
of that then you won't even need to rebase anything.

Thanks,

	Ingo

  reply	other threads:[~2018-10-02  8:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27  8:50 [GIT PULL 00/11] EFI updates for v4.20 Ard Biesheuvel
2018-09-27  8:50 ` [PATCH 01/11] efi: honour memory reservations passed via a linux specific config table Ard Biesheuvel
2018-09-27  8:50 ` [PATCH 02/11] efi/arm: libstub: add a root memreserve " Ard Biesheuvel
2018-09-27  8:50 ` [PATCH 03/11] efi: add API to reserve memory persistently across kexec reboot Ard Biesheuvel
2018-09-27  8:50 ` [PATCH 04/11] efi/libstub: arm: support building with clang Ard Biesheuvel
2018-09-27  8:50 ` [PATCH 05/11] efi/efi_test: add exporting ResetSystem runtime service Ard Biesheuvel
2018-09-27  8:50 ` [PATCH 06/11] efi: Make efi_rts_work accessible to efi page fault handler Ard Biesheuvel
2018-09-27  8:50 ` [PATCH 07/11] efi/x86: Handle page faults occurring while running EFI runtime services Ard Biesheuvel
2018-09-27  8:50 ` [PATCH 08/11] efi/x86: drop task_lock() from efi_switch_mm() Ard Biesheuvel
2018-09-27  8:50 ` [PATCH 09/11] efi/x86: earlyprintk - Add 64bit efi fb address support Ard Biesheuvel
2018-09-27  8:50 ` [PATCH 10/11] efi/x86: Call efi_parse_options() from efi_main() Ard Biesheuvel
2018-09-27  8:50 ` [PATCH 11/11] x86: boot: Fix EFI stub alignment Ard Biesheuvel
2018-09-27  9:07 ` [GIT PULL 00/11] EFI updates for v4.20 Marc Zyngier
2018-10-02  8:34   ` Ingo Molnar
2018-10-02  8:38     ` Ingo Molnar [this message]
2018-10-02  9:26       ` Ard Biesheuvel
2018-10-02  9:29       ` Marc Zyngier

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=20181002083817.GC120270@gmail.com \
    --to=mingo@kernel.org \
    --cc=aaron.ma@canonical.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=astrachan@google.com \
    --cc=ben@decadent.org.uk \
    --cc=bhsharma@redhat.com \
    --cc=bigeasy@linutronix.de \
    --cc=hdegoede@redhat.com \
    --cc=ivan.hu@canonical.com \
    --cc=jeremy.linton@arm.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=matt@codeblueprint.co.uk \
    --cc=pbrobinson@redhat.com \
    --cc=sai.praneeth.prakhya@intel.com \
    --cc=stefan@agner.ch \
    --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