All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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 11:27:34 +0200	[thread overview]
Message-ID: <bd5308eb-57a3-4484-8be6-b41ee30233ae@linux.intel.com> (raw)
In-Reply-To: <2025041011-borrowing-shrug-781e@gregkh>

Hi,

On 4/10/2025 10:03 AM, Greg Kroah-Hartman wrote:
> 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.

Yeah, sorry about that. It seems I'm still learning the art of patience in the kernel processes.
I didn't mean to rush anything. I was just worried my patch might have been overlooked due to a typo or a wrong commit message tag.

I'll make sure to review the backported patches in the meantime.

And thanks for holding back on the rant. I really think that the standard set by Linus is not healthy.

Regards,
Jacek


  reply	other threads:[~2025-04-10  9:28 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
2025-04-10  9:27     ` Jacek Lawrynowicz [this message]
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=bd5308eb-57a3-4484-8be6-b41ee30233ae@linux.intel.com \
    --to=jacek.lawrynowicz@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --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 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.