lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 2 Oct 2018 10:34:56 +0200
From:   Ingo Molnar <mingo@...nel.org>
To:     Marc Zyngier <marc.zyngier@....com>
Cc:     Ard Biesheuvel <ard.biesheuvel@...aro.org>,
        linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
        linux-efi@...r.kernel.org, Aaron Ma <aaron.ma@...onical.com>,
        Alistair Strachan <astrachan@...gle.com>,
        Ben Hutchings <ben@...adent.org.uk>,
        Bhupesh Sharma <bhsharma@...hat.com>,
        Hans de Goede <hdegoede@...hat.com>,
        Ivan Hu <ivan.hu@...onical.com>,
        Jeremy Linton <jeremy.linton@....com>,
        Matt Fleming <matt@...eblueprint.co.uk>,
        Peter Robinson <pbrobinson@...hat.com>,
        Sai Praneeth Prakhya <sai.praneeth.prakhya@...el.com>,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        Stefan Agner <stefan@...er.ch>
Subject: Re: [GIT PULL 00/11] EFI updates for v4.20


* Marc Zyngier <marc.zyngier@....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?

Thanks,

	Ingo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ