From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Karol Wachowski <karol.wachowski@intel.com>
Subject: Re: [PATCH] accel/ivpu: Add handling of VPU_JSM_STATUS_MVNCI_CONTEXT_VIOLATION_HW
Date: Thu, 10 Apr 2025 10:03:56 +0200 [thread overview]
Message-ID: <2025041011-borrowing-shrug-781e@gregkh> (raw)
In-Reply-To: <8d96c75d-e8fb-446b-a85c-803a2b5212ed@linux.intel.com>
On Thu, Apr 10, 2025 at 09:49:37AM +0200, Jacek Lawrynowicz wrote:
> Hi,
>
> This is an important patch for the Intel NPU.
> Is there anything it is missing to be included in stable?
Patience, you only sent this:
> On 4/8/2025 11:57 AM, Jacek Lawrynowicz wrote:
2 days ago, AFTER the latest of -rc releases was sent out for review,
and those kernels have NOT even been released yet!
[rant about how you all know this process works deleted as it was
just snarky on my side, although quite cathartic, thanks for letting me
vent...]
Relax, it will get handled when we can get to it. To help out, please
take the time to review pending stable backported patches that have been
submitted to the mailing list ahead of yours.
greg k-h
next prev parent reply other threads:[~2025-04-10 8:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 9:57 [PATCH] accel/ivpu: Add handling of VPU_JSM_STATUS_MVNCI_CONTEXT_VIOLATION_HW Jacek Lawrynowicz
2025-04-10 7:49 ` Jacek Lawrynowicz
2025-04-10 8:03 ` Greg Kroah-Hartman [this message]
2025-04-10 9:27 ` Jacek Lawrynowicz
2025-04-10 15:53 ` Sasha Levin
2025-04-22 12:17 ` Greg KH
2025-04-24 10:22 ` Jacek Lawrynowicz
2025-04-24 10:34 ` Greg KH
2025-04-30 12:50 ` Jacek Lawrynowicz
-- strict thread matches above, loose matches on Subject: below --
2025-04-01 11:08 Jacek Lawrynowicz
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=2025041011-borrowing-shrug-781e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=karol.wachowski@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox