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 FW log patches to 6.12
Date: Tue, 20 May 2025 12:22:46 +0200 [thread overview]
Message-ID: <2025052040-struck-status-997a@gregkh> (raw)
In-Reply-To: <a0f38bde-d782-4170-9736-f1ad14a13ba6@linux.intel.com>
On Tue, May 13, 2025 at 06:26:28PM +0200, Jacek Lawrynowicz wrote:
> Hi,
>
> Please cherry-pick following 4 patches to 6.12:
> 3a3fb8110c65d361cd9d750c9e16520f740c93f2 accel/ivpu: Rename ivpu_log_level to fw_log_level
> 4b4d9e394b6f45ac26ac6144b31604c76b7e3705 accel/ivpu: Reset fw log on cold boot
> 1fc1251149a76d3b75d7f4c94d9c4e081b7df6b4 accel/ivpu: Refactor functions in ivpu_fw_log.c
> 4bc988b47019536b3b1f7d9c5b83893c712d94d6 accel/ivpu: Fix fw log printing
>
> These are fixing some firmware log corner cases that allow us to get reliable output in case of a failure.
> They should apply without conflicts.
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2025-05-20 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 16:26 Request for backporting accel/ivpu FW log patches to 6.12 Jacek Lawrynowicz
2025-05-20 10:22 ` Greg KH [this message]
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=2025052040-struck-status-997a@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