Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Cc: stable@vger.kernel.org
Subject: Re: Request for backporting accel/ivpu PTL patches to 6.12
Date: Wed, 4 Jun 2025 15:21:14 +0200	[thread overview]
Message-ID: <2025060411-tableful-outage-4006@gregkh> (raw)
In-Reply-To: <fe7c8681-83de-4f3e-8dab-04185f0f9416@linux.intel.com>

On Tue, Jun 03, 2025 at 12:42:09PM +0200, Jacek Lawrynowicz wrote:
> Hi,
> 
> Please cherry-pick following 9 patches to 6.12:
> 525a3858aad73 accel/ivpu: Set 500 ns delay between power island TRICKLE and ENABLE
> 08eb99ce911d3 accel/ivpu: Do not fail on cmdq if failed to allocate preemption buffers
> 755fb86789165 accel/ivpu: Use whole user and shave ranges for preemption buffers
> 98110eb5924bd accel/ivpu: Increase MS info buffer size
> c140244f0cfb9 accel/ivpu: Add initial Panther Lake support
> 88bdd1644ca28 accel/ivpu: Update power island delays
> ce68f86c44513 accel/ivpu: Do not fail when more than 1 tile is fused
> 83b6fa5844b53 accel/ivpu: Increase DMA address range
> e91191efe75a9 accel/ivpu: Move secondary preemption buffer allocation to DMA range
> 
> These add support for new Panther Lake HW.
> They should apply without conflicts.

That's way larger than the normal "add a new quirk or device id" patch
for new device support, right?  Why do you feel this is needed and
relevant for 6.12.y and meets the requirements that we have for stable
kernel patches?

thanks,

greg k-h

  reply	other threads:[~2025-06-04 13:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03 10:42 Request for backporting accel/ivpu PTL patches to 6.12 Jacek Lawrynowicz
2025-06-04 13:21 ` Greg KH [this message]
2025-06-06 12:09   ` Jacek Lawrynowicz
2025-06-07  7:10     ` Greg KH

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=2025060411-tableful-outage-4006@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jacek.lawrynowicz@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox