From: david.vrabel@citrix.com (David Vrabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [Xen-devel] [GIT PULL] EFI ARM Xen support
Date: Tue, 17 May 2016 11:40:14 +0100 [thread overview]
Message-ID: <573AF50E.9090206@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1605171109170.2494@sstabellini-ThinkPad-X260>
On 17/05/16 11:12, Stefano Stabellini wrote:
> On Sat, 14 May 2016, Matt Fleming wrote:
>> Folks,
>>
>> Please pull the following branch which contains support for Xen on ARM
>> EFI platforms.
>>
>> This merge includes a merge of Stefano's xen/linux-next branch to pull
>> in the prerequisites required for Shannon's commit:
>>
>> 11ee5491e5ff ("Xen: EFI: Parse DT parameters for Xen specific UEFI")
>>
>> as it needs both the latest changes in the EFI 'next' branch (now
>> tip/efi/core) and xen/linux-next.
>>
>> I have intentionally not included the individual patches as I would
>> normally do in a pull request, so that commit history created by my
>> merging of Stefano's branch is preserved, and so that there's no way
>> to accidentally apply the patches individually.
>>
>> The following changes since commit 6c5450ef66816216e574885cf8d3ddb31ef77428:
>>
>> efivarfs: Make efivarfs_file_ioctl() static (2016-05-07 07:06:13 +0200)
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git efi/arm-xen
>>
>> for you to fetch changes up to 11ee5491e5ff519e0d3a7018eb21351cb6955a98:
>>
>> Xen: EFI: Parse DT parameters for Xen specific UEFI (2016-05-14 19:31:01 +0100)
>
> Is this arrangement working for everybody, in particular the tip
> maintainers?
Yes.
David
next prev parent reply other threads:[~2016-05-17 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 19:04 [GIT PULL] EFI ARM Xen support Matt Fleming
2016-05-17 10:12 ` Stefano Stabellini
2016-05-17 10:40 ` David Vrabel [this message]
2016-05-17 12:57 ` [Xen-devel] " Stefano Stabellini
2016-05-18 10:46 ` Ingo Molnar
2016-05-18 10:49 ` Matt Fleming
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=573AF50E.9090206@citrix.com \
--to=david.vrabel@citrix.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).