public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
	Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v2 1/7] accel/ivpu: Make DB_ID and JOB_ID allocations incremental
Date: Thu,  8 May 2025 12:19:43 -0400	[thread overview]
Message-ID: <20250507115642-348e239c584214d6@stable.kernel.org> (raw)
In-Reply-To: <20250505103334.79027-2-jacek.lawrynowicz@linux.intel.com>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: c3b0ec0fe0c7ebc4eb42ba60f7340ecdb7aae1a2

WARNING: Author mismatch between patch and upstream commit:
Backport author: Jacek Lawrynowicz<jacek.lawrynowicz@linux.intel.com>
Commit author: Tomasz Rusinowicz<tomasz.rusinowicz@intel.com>

Note: The patch differs from the upstream commit:
---
1:  c3b0ec0fe0c7e < -:  ------------- accel/ivpu: Make DB_ID and JOB_ID allocations incremental
-:  ------------- > 1:  aeaee199900ee Linux 6.14.5
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.4.y        |  Success    |  Success   |

  reply	other threads:[~2025-05-08 16:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05 10:33 [PATCH v2 0/7] accel/ivpu: Add context violation handling for 6.12 Jacek Lawrynowicz
2025-05-05 10:33 ` [PATCH v2 1/7] accel/ivpu: Make DB_ID and JOB_ID allocations incremental Jacek Lawrynowicz
2025-05-08 16:19   ` Sasha Levin [this message]
2025-05-05 10:33 ` [PATCH v2 2/7] accel/ivpu: Use xa_alloc_cyclic() instead of custom function Jacek Lawrynowicz
2025-05-08 16:18   ` Sasha Levin
2025-05-05 10:33 ` [PATCH v2 3/7] accel/ivpu: Fix a typo Jacek Lawrynowicz
2025-05-08 16:18   ` Sasha Levin
2025-05-05 10:33 ` [PATCH v2 4/7] accel/ivpu: Update VPU FW API headers Jacek Lawrynowicz
2025-05-08 16:17   ` Sasha Levin
2025-05-05 10:33 ` [PATCH v2 5/7] accel/ivpu: Abort all jobs after command queue unregister Jacek Lawrynowicz
2025-05-08 16:17   ` Sasha Levin
2025-05-05 10:33 ` [PATCH v2 6/7] accel/ivpu: Fix locking order in ivpu_job_submit Jacek Lawrynowicz
2025-05-08 16:18   ` Sasha Levin
2025-05-05 10:33 ` [PATCH v2 7/7] accel/ivpu: Add handling of VPU_JSM_STATUS_MVNCI_CONTEXT_VIOLATION_HW Jacek Lawrynowicz
2025-05-08 16:19   ` Sasha Levin

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=20250507115642-348e239c584214d6@stable.kernel.org \
    --to=sashal@kernel.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