From: Joerg Roedel <joro@8bytes.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
iommu@lists.linux-foundation.org
Subject: Re: [PATCH v3 1/2] iommu: Disable preemption around use of this_cpu_ptr()
Date: Mon, 27 Jun 2016 13:19:25 +0200 [thread overview]
Message-ID: <20160627111925.GJ11432@8bytes.org> (raw)
In-Reply-To: <7b6bfcfc-093a-f90f-94b0-0e89dde8c0e6@leemhuis.info>
On Sun, Jun 26, 2016 at 12:54:19PM +0200, Thorsten Leemhuis wrote:
> Joerg, what's the status here? This made it on my 4.7 regressions
> report, as the patches from this thread are supposed to fix a
> regression; see
> http://thread.gmane.org/gmane.linux.usb.general/143504/focus=153154
> for details.
>
> Please let me know if if fixes went to mainline already; I did a quick
> check and could see any.
Okay, queued the fix, should be upstream for -rc6.
> Sincerely, your regression tracker for Linux 4.7 (http://bit.ly/28JRmJo)
> Thorsten
Awesome, glad to see you picking this up :)
Cheers,
Joerg
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-06-27 11:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 16:34 [PATCH] iommu: Disable preemption around use of this_cpu_ptr() Chris Wilson
2016-06-01 10:23 ` [PATCH v2] " Chris Wilson
2016-06-01 11:10 ` [PATCH v3 1/2] " Chris Wilson
2016-06-01 11:10 ` [PATCH v3 2/2] iommu: Remove cpu-local spinlock Chris Wilson
2016-06-01 12:40 ` Joonas Lahtinen
[not found] ` <1464779409-26711-2-git-send-email-chris-Y6uKTt2uX1cEflXRtASbqLVCufUGDwFn@public.gmane.org>
2016-06-15 12:22 ` Joerg Roedel
2016-06-01 12:25 ` [PATCH v3 1/2] iommu: Disable preemption around use of this_cpu_ptr() Joonas Lahtinen
2016-06-15 12:25 ` Joerg Roedel
2016-06-26 10:54 ` Thorsten Leemhuis
2016-06-27 11:19 ` Joerg Roedel [this message]
2016-06-27 11:14 ` 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=20160627111925.GJ11432@8bytes.org \
--to=joro@8bytes.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
/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).