From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [GIT PULL 00/11] EFI updates for v4.20 Date: Tue, 2 Oct 2018 10:34:56 +0200 Message-ID: <20181002083456.GB120270@gmail.com> References: <20180927085039.8391-1-ard.biesheuvel@linaro.org> <7c25a402-0fc8-fe70-ac95-348a93f4fe69@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <7c25a402-0fc8-fe70-ac95-348a93f4fe69@arm.com> Sender: linux-kernel-owner@vger.kernel.org To: Marc Zyngier Cc: Ard Biesheuvel , linux-kernel@vger.kernel.org, Thomas Gleixner , linux-efi@vger.kernel.org, Aaron Ma , Alistair Strachan , Ben Hutchings , Bhupesh Sharma , Hans de Goede , Ivan Hu , Jeremy Linton , Matt Fleming , Peter Robinson , Sai Praneeth Prakhya , Sebastian Andrzej Siewior , Stefan Agner List-Id: linux-efi@vger.kernel.org * Marc Zyngier 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? Thanks, Ingo