From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
To: iommu@lists.linux-foundation.org
Cc: , Joerg Roedel <jroedel@suse.de>,
intel-gfx@lists.freedesktop.org, stable@vger.kernel.org,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] iommu/iova: Remove stale cached32_node
Date: Sat, 20 Jul 2019 21:47:00 +0000 [thread overview]
Message-ID: <20190720214701.544FD20838@mail.kernel.org> (raw)
In-Reply-To: <20190720180848.15192-1-chris@chris-wilson.co.uk>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: e60aa7b53845 iommu/iova: Extend rbtree node caching.
The bot has tested the following trees: v5.2.1, v5.1.18, v4.19.59.
v5.2.1: Build OK!
v5.1.18: Build OK!
v4.19.59: Failed to apply! Possible dependencies:
bee60e94a1e2 ("iommu/iova: Optimise attempts to allocate iova from 32bit address range")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Sasha Levin <sashal-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Chris Wilson
<chris-Y6uKTt2uX1cEflXRtASbqLVCufUGDwFn@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Cc: Joerg Roedel <jroedel-l3A5Bk7waGM@public.gmane.org>,
intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Subject: Re: [PATCH] iommu/iova: Remove stale cached32_node
Date: Sat, 20 Jul 2019 21:47:00 +0000 [thread overview]
Message-ID: <20190720214701.544FD20838@mail.kernel.org> (raw)
In-Reply-To: <20190720180848.15192-1-chris-Y6uKTt2uX1cEflXRtASbqLVCufUGDwFn@public.gmane.org>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: e60aa7b53845 iommu/iova: Extend rbtree node caching.
The bot has tested the following trees: v5.2.1, v5.1.18, v4.19.59.
v5.2.1: Build OK!
v5.1.18: Build OK!
v4.19.59: Failed to apply! Possible dependencies:
bee60e94a1e2 ("iommu/iova: Optimise attempts to allocate iova from 32bit address range")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-07-20 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 18:08 [PATCH] iommu/iova: Remove stale cached32_node Chris Wilson
2019-07-20 18:08 ` Chris Wilson
2019-07-20 18:58 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-07-20 21:47 ` Sasha Levin [this message]
2019-07-20 21:47 ` [PATCH] " Sasha Levin
2019-07-20 21:47 ` Sasha Levin
2019-07-22 10:13 ` Robin Murphy
2019-07-22 10:13 ` Robin Murphy
2019-07-22 10:46 ` Chris Wilson
2019-07-22 10:46 ` Chris Wilson
2019-07-22 15:51 ` Joerg Roedel
2019-07-22 15:51 ` Joerg Roedel
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=20190720214701.544FD20838@mail.kernel.org \
--to=sashal@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jroedel@suse.de \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.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.