From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>, linux@armlinux.org.uk
Cc: xen-devel@lists.xen.org, jgross@suse.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org, boris.ostrovsky@oracle.com,
linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com
Subject: Re: [PATCH 1/2] xen/arm, arm64: fix xen_dma_ops after 815dd18 "Consolidate get_dma_ops..."
Date: Tue, 25 Apr 2017 13:51:22 +0100 [thread overview]
Message-ID: <f0667d8c-1c17-8d5f-a5d7-1e0d014e86ec@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1704241214100.16723@sstabellini-ThinkPad-X260>
Hi Stefano,
On 24/04/17 20:16, Stefano Stabellini wrote:
> Given the outstanding regression we need to fix as soon as possible,
> I'll queue these patches on the xentip tree for 4.12.
It looks like there is another rc for 4.11. I am wondering whether you
could try to send a pull request to Linus so it can be fixed in 4.11?
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2017-04-25 12:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 21:04 [PATCH 1/2] xen/arm,arm64: fix xen_dma_ops after 815dd18 "Consolidate get_dma_ops..." Stefano Stabellini
2017-04-13 21:04 ` [PATCH 2/2] xen/arm,arm64: rename __generic_dma_ops to xen_get_dma_ops Stefano Stabellini
2017-04-14 0:48 ` Boris Ostrovsky
2017-04-14 2:14 ` Konrad Rzeszutek Wilk
2017-04-18 14:21 ` [PATCH 1/2] xen/arm, arm64: fix xen_dma_ops after 815dd18 "Consolidate get_dma_ops..." Catalin Marinas
2017-04-19 17:25 ` Stefano Stabellini
2017-04-19 18:20 ` Juergen Gross
2017-04-19 18:32 ` Stefano Stabellini
2017-04-24 19:16 ` Stefano Stabellini
2017-04-25 12:51 ` Julien Grall [this message]
2017-04-25 17:22 ` Stefano Stabellini
2017-04-26 11:19 ` Catalin Marinas
2017-04-26 17:00 ` Stefano Stabellini
2017-04-26 17:13 ` Catalin Marinas
2017-04-26 17:17 ` Stefano Stabellini
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=f0667d8c-1c17-8d5f-a5d7-1e0d014e86ec@arm.com \
--to=julien.grall@arm.com \
--cc=boris.ostrovsky@oracle.com \
--cc=catalin.marinas@arm.com \
--cc=jgross@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=sstabellini@kernel.org \
--cc=will.deacon@arm.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 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).