All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	"Luis R. Rodriguez" <mcgrof@kernel.org>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Xen Devel <Xen-devel@lists.xensource.com>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shannon Zhao <shannon.zhao@linaro.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Borislav Petkov <bp@alien8.de>
Subject: Re: efi_enabled(EFI_PARAVIRT) use
Date: Fri, 29 Apr 2016 12:46:21 +0200	[thread overview]
Message-ID: <20160429104621.GA6354@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1604291123260.3312@sstabellini-ThinkPad-X260>


* Stefano Stabellini <sstabellini@kernel.org> wrote:

> On Fri, 29 Apr 2016, Ingo Molnar wrote:
> > Also, it would be nice to have all things EFI in a single tree, the conflicts are 
> > going to be painful! There's very little reason not to carry this kind of commit:
> > 
> >  arch/arm/xen/enlighten.c           |  6 +++++
> >  drivers/firmware/efi/arm-runtime.c | 17 +++++++++-----
> >  drivers/firmware/efi/efi.c         | 45 ++++++++++++++++++++++++++++++++------
> >  3 files changed, 56 insertions(+), 12 deletions(-)
> > 
> > in the EFI tree.
> 
> That's true. I'll drop this commit from xentip and let Matt pick it up
> or request changes as he sees fit.

Thanks!

	Ingo

  reply	other threads:[~2016-04-29 10:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29  4:20 linux-next: manual merge of the xen-tip tree with the tip tree Stephen Rothwell
2016-04-29  6:39 ` efi_enabled(EFI_PARAVIRT) use Ingo Molnar
2016-04-29  6:39   ` Ingo Molnar
2016-04-29  8:25   ` Borislav Petkov
2016-04-29  9:26     ` Matt Fleming
2016-04-29 10:34   ` Stefano Stabellini
2016-04-29 10:46     ` Ingo Molnar [this message]
2016-04-29 14:39     ` Matt Fleming
2016-04-29 14:53       ` Ard Biesheuvel
2016-04-30 14:14         ` Shannon Zhao
2016-04-30 20:44           ` Matt Fleming
2016-05-01  3:24             ` Shannon Zhao
2016-05-01 13:26               ` Matt Fleming
2016-05-01 14:36                 ` Shannon Zhao
2016-05-02 10:45                   ` Matt Fleming
2016-05-03  1:45                     ` [Xen-devel] " Shannon Zhao
2016-05-03  1:45                       ` Shannon Zhao
2016-05-04 11:36                       ` Matt Fleming
2016-05-03  9:13           ` Shannon Zhao
2016-05-03  9:13             ` Shannon Zhao
2016-04-29 14:58       ` Stefano Stabellini
2016-04-29 15:37         ` Stefano Stabellini
2016-04-30 14:04           ` Shannon Zhao

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=20160429104621.GA6354@gmail.com \
    --to=mingo@kernel.org \
    --cc=Xen-devel@lists.xensource.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=mcgrof@kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=shannon.zhao@linaro.org \
    --cc=sstabellini@kernel.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.