From: Linus Torvalds <torvalds@linux-foundation.org>
To: konrad@darnok.org
Cc: xen-devel@lists.xen.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
joe.jin@oracle.com
Subject: Re: [GIT PULL] (xen-swiotlb) stable/for-linus-4.20
Date: Tue, 23 Oct 2018 11:05:54 +0100 [thread overview]
Message-ID: <CAHk-=whKtd8WArFUjBmszD8-+t5BbbVOwUYqWvgRn49g=f-dpg@mail.gmail.com> (raw)
In-Reply-To: <20181022193304.GC20677@dhcp-10-175-29-12.vpn.oracle.com>
On Mon, Oct 22, 2018 at 8:33 PM Konrad Rzeszutek Wilk <konrad@darnok.org> wrote:
>
> one tiny fix for the Xen SWIOTLB mechanism that occasionally happened with
> devices that didn't allocate size in power of two but rather some odd
> sizes. We neglected to make the memory coherent leading to all kinds of fun crashes.
Pulled,
Linus
prev parent reply other threads:[~2018-10-23 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 19:33 [GIT PULL] (xen-swiotlb) stable/for-linus-4.20 Konrad Rzeszutek Wilk
2018-10-23 10:05 ` Linus Torvalds [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='CAHk-=whKtd8WArFUjBmszD8-+t5BbbVOwUYqWvgRn49g=f-dpg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=joe.jin@oracle.com \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--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).