From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
Punit Agrawal <punit.agrawal@arm.com>
Cc: wei.liu2@citrix.com, George.Dunlap@eu.citrix.com,
andrew.cooper3@citrix.com, tim@xen.org, xen-devel@lists.xen.org,
jbeulich@suse.com, ian.jackson@eu.citrix.com
Subject: Re: [For Xen-4.10 PATCH v2 0/3] Reduce unnecessary icache maintenance operations
Date: Wed, 7 Jun 2017 18:47:22 +0100 [thread overview]
Message-ID: <156c952a-a755-89b2-ab90-553b54136421@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1706071045570.26108@sstabellini-ThinkPad-X260>
On 07/06/17 18:46, Stefano Stabellini wrote:
> On Wed, 7 Jun 2017, Punit Agrawal wrote:
>> Stefano Stabellini <sstabellini@kernel.org> writes:
>>
>>> On Tue, 6 Jun 2017, Julien Grall wrote:
>>>> On 26/05/17 12:14, Punit Agrawal wrote:
>>>>> Hi,
>>>>
>>>> Hi,
>>>>
>>>> It looks like this patch series has been fully acked. Can someone apply it?
>>>
>>> Done. It was appropriately marked in my inbox, but I was somehow
>>> reluctant to commit things until the release is done. I guess I don't
>>> need to be. I committed the series now.
>>
>> Thanks Stefano for merging the series. As osstest discovered, there is a
>> build failure on x86 due to the last patch. I've send a fix[0] for it.
>>
>> If the fix looks good, could you merge it as well.
>>
>> [0] <20170607093449.25607-1-punit.agrawal@arm.com>
>
> I noticed, but that patch affects x86, so it needs an ack from one of
> the x86 maintainers.
Jan already merged it.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-06-07 17:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 11:14 [For Xen-4.10 PATCH v2 0/3] Reduce unnecessary icache maintenance operations Punit Agrawal
2017-05-26 11:14 ` [For Xen-4.10 PATCH v2 1/3] Allow control of icache invalidations when calling flush_page_to_ram() Punit Agrawal
2017-05-26 11:14 ` [For Xen-4.10 PATCH v2 2/3] arm: p2m: Prevent redundant icache flushes Punit Agrawal
2017-05-26 11:14 ` [For Xen-4.10 PATCH v2 3/3] Avoid excess icache flushes in populate_physmap() before domain has been created Punit Agrawal
2017-05-26 11:51 ` Jan Beulich
2017-06-07 8:38 ` Jan Beulich
2017-06-07 8:59 ` Punit Agrawal
2017-06-07 9:34 ` [For Xen-4.10 PATCH] Ensure invalidate_icache() definition is visible only when !__ASSEMBLY__ Punit Agrawal
2017-06-07 10:37 ` Jan Beulich
2017-06-07 11:19 ` [For Xen-4.10 PATCH v2 3/3] Avoid excess icache flushes in populate_physmap() before domain has been created Andrew Cooper
2017-06-07 11:32 ` Julien Grall
2017-06-07 11:41 ` Punit Agrawal
2017-06-07 12:04 ` [For Xen-4.10 PATCH] memory: Re-introduce an erroneously dropped line Punit Agrawal
2017-06-07 12:13 ` Jan Beulich
2017-06-07 12:16 ` Julien Grall
2017-06-06 16:32 ` [For Xen-4.10 PATCH v2 0/3] Reduce unnecessary icache maintenance operations Julien Grall
2017-06-06 16:36 ` Jan Beulich
2017-06-06 18:51 ` Stefano Stabellini
2017-06-07 9:46 ` Punit Agrawal
2017-06-07 17:46 ` Stefano Stabellini
2017-06-07 17:47 ` Julien Grall [this message]
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=156c952a-a755-89b2-ab90-553b54136421@arm.com \
--to=julien.grall@arm.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=punit.agrawal@arm.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 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.