From: Joerg Roedel <joro@8bytes.org>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: iommu@lists.linux.dev, suravee.suthikulpanit@amd.com,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH] iommu/amd: Fix workqueue name
Date: Tue, 4 Jun 2024 13:59:01 +0200 [thread overview]
Message-ID: <Zl8BhTVAuO30dvLK@8bytes.org> (raw)
In-Reply-To: <20240529113900.5798-1-vasant.hegde@amd.com>
On Wed, May 29, 2024 at 11:39:00AM +0000, Vasant Hegde wrote:
> Workqueue name length is crossing WQ_NAME_LEN limit. Fix it by changing
> name format. New format : "iopf_queue/amdvi-<iommu-devid>"
>
> kernel warning:
> [ 11.146912] workqueue: name exceeds WQ_NAME_LEN. Truncating to: iopf_queue/amdiommu-0xc002-iopf
>
> Reported-by: Borislav Petkov <bp@alien8.de>
> Fixes: 61928bab9d26 ("iommu/amd: Define per-IOMMU iopf_queue")
> Signed-off-by: Vasant Hegde <vasant.hegde@amd.com>
> ---
> drivers/iommu/amd/ppr.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2024-06-04 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 11:39 [PATCH] iommu/amd: Fix workqueue name Vasant Hegde
2024-05-29 14:51 ` Borislav Petkov
2024-06-04 11:59 ` Joerg Roedel [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=Zl8BhTVAuO30dvLK@8bytes.org \
--to=joro@8bytes.org \
--cc=bp@alien8.de \
--cc=iommu@lists.linux.dev \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
/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