From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
<linux-kernel@vger.kernel.org>, Will Deacon <will.deacon@arm.com>
Subject: Re: swiotlb on arm status
Date: Fri, 8 Nov 2013 18:56:43 +0000 [thread overview]
Message-ID: <alpine.DEB.2.02.1311081854530.26077@kaball.uk.xensource.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1311061245580.26077@kaball.uk.xensource.com>
Russell,
sorry to harass you again, but I am starting to be worried about missing
the merge window. Could you please take a last look at these patches?
On Wed, 6 Nov 2013, Stefano Stabellini wrote:
> Hi Russell,
> I thought about giving you a quick summary of the status of the swiotlb
> patch series on ARM: it has been in linux-next since last week, a few
> issues were found and fixed already.
>
> I went through all the patches and I am still missing few acks on the
> arm specific bits:
>
> http://marc.info/?l=linux-kernel&m=138359037113882&w=2
> The latest version of the "make SWIOTLB available" patch, on which you
> have already commented in the past. This version should address your
> previous feedback.
>
> http://marc.info/?l=linux-kernel&m=138269913107769&w=2
> This one is about not merging bio_vecs on Xen. The idea and the code is
> taken from x86. The arm64 part has been acked by Catalin, but the arm32
> part is still missing an ack. It introduces a build issue on
> ape6evm_defconfig, fixed separately by the patch below.
>
> http://marc.info/?l=linux-kernel&m=138374169030300&w=2
> A fix for the build issue found by Olof on linux-next on
> ape6evm_defconfig.
>
> Cheers,
>
> Stefano
next prev parent reply other threads:[~2013-11-08 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 16:22 Stefano Stabellini
2013-11-08 18:56 ` Stefano Stabellini [this message]
2013-11-08 19:38 ` Russell King - ARM Linux
2013-11-08 19:42 ` 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=alpine.DEB.2.02.1311081854530.26077@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=will.deacon@arm.com \
/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
all inboxes | Powered by JetHome®