From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [topic/core-for-CI][PATCH 0/2] Drop some unnecessary patches
Date: Wed, 25 Oct 2023 14:41:50 +0300 [thread overview]
Message-ID: <87r0lj7wu9.fsf@intel.com> (raw)
In-Reply-To: <20231024175552.15503-1-ville.syrjala@linux.intel.com>
On Tue, 24 Oct 2023, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Try to drop a few seemingly unnecessary patches from core-for-CI.
Yay, ack!
>
> Ville Syrjälä (2):
> Revert "freezer: Dump more info on whoever is trying to get frozen
> with locks held"
> Revert "iommu: Remove iova cpu hotplugging flushing"
>
> drivers/iommu/iova.c | 28 ++++++++++++++++++++++++++++
> include/linux/cpuhotplug.h | 1 +
> include/linux/iova.h | 1 +
> kernel/freezer.c | 12 ++----------
> 4 files changed, 32 insertions(+), 10 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-10-25 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 17:55 [Intel-gfx] [topic/core-for-CI][PATCH 0/2] Drop some unnecessary patches Ville Syrjala
2023-10-24 17:55 ` [Intel-gfx] [topic/core-for-CI][PATCH 1/2] Revert "freezer: Dump more info on whoever is trying to get frozen with locks held" Ville Syrjala
2023-10-24 17:55 ` [Intel-gfx] [topic/core-for-CI][PATCH 2/2] Revert "iommu: Remove iova cpu hotplugging flushing" Ville Syrjala
2023-10-25 5:04 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Drop some unnecessary patches Patchwork
2023-10-25 5:04 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-25 5:18 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-25 11:41 ` Jani Nikula [this message]
2023-10-26 12:41 ` [Intel-gfx] [topic/core-for-CI][PATCH 0/2] " Ville Syrjälä
2023-10-25 20:58 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
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=87r0lj7wu9.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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