From: Bart Van Assche <bvanassche@acm.org>
To: "Bartłomiej Kubik" <kubik.bartlomiej@gmail.com>
Cc: sathya.prakash@broadcom.com, kashyap.desai@broadcom.com,
sumit.saxena@broadcom.com, sreekanth.reddy@broadcom.com,
martin.petersen@oracle.com, mpi3mr-linuxdrv.pdl@broadcom.com,
linux-scsi@vger.kernel.org, skhan@linuxfoundation.org,
khalid@kernel.org, david.hunter.linux@gmail.com,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFT v2] driver/scsi/mpi3mr: Fix build warning for mpi3mr_start_watchdog
Date: Sat, 15 Nov 2025 06:47:18 -0800 [thread overview]
Message-ID: <d5185412-d49b-425f-85c5-54f0974818f1@acm.org> (raw)
In-Reply-To: <CAPqLRf2eyK2bRess785AB6C2+Mj4U1CGyT6n4spkJy+_gNc9-A@mail.gmail.com>
On 11/15/25 6:31 AM, Bartłomiej Kubik wrote:
>>> diff --git a/drivers/scsi/mpi3mr/mpi3mr_fw.c b/drivers/scsi/mpi3mr/mpi3mr_fw.c
>>> index 8fe6e0bf342e..18b176e358c5 100644
>>> --- a/drivers/scsi/mpi3mr/mpi3mr_fw.c
>>> +++ b/drivers/scsi/mpi3mr/mpi3mr_fw.c
>>> @@ -2879,8 +2879,7 @@ void mpi3mr_start_watchdog(struct mpi3mr_ioc *mrioc)
>>>
>>> INIT_DELAYED_WORK(&mrioc->watchdog_work, mpi3mr_watchdog_work);
>>> snprintf(mrioc->watchdog_work_q_name,
>>> - sizeof(mrioc->watchdog_work_q_name), "watchdog_%s%d", mrioc->name,
>>> - mrioc->id);
>>> + sizeof(mrioc->watchdog_work_q_name), "watchdog_%s", mrioc->name);
>>> mrioc->watchdog_work_q = alloc_ordered_workqueue(
>>> "%s", WQ_MEM_RECLAIM, mrioc->watchdog_work_q_name);
>>> if (!mrioc->watchdog_work_q) {
>> Leaving out mrioc->id from the workqueue name seems like an unacceptable
>> behavior change to me.
>
> Add twice the same ID one after one. Is it not a mistake ??
> If mrioc->name has that same ID at the end.
>
> sprintf(mrioc->name, "%s%d", mrioc->driver_name, mrioc->id)
>
> watchdog_work_q_name is built from mrioc->name which has this ID at the end.
> If I see correctly, if mrioc->id will be 1 then watchdog_work_q_name
> will look like
> watchdog_mpi3mr11, but I think it should be watchdog_mpi3mr1, or am I missing
> something??
I'm not sure - I'm not familiar myself with the mpi3mr driver. I will
let someone who is familiar with this driver comment on this.
Thanks,
Bart.
prev parent reply other threads:[~2025-11-15 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 14:55 Bartlomiej Kubik
2025-11-12 20:29 ` Bartłomiej Kubik
2025-11-12 20:55 ` Bart Van Assche
2025-11-15 13:47 ` Bartłomiej Kubik
2025-11-15 14:31 ` Bartłomiej Kubik
2025-11-15 14:47 ` Bart Van Assche [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=d5185412-d49b-425f-85c5-54f0974818f1@acm.org \
--to=bvanassche@acm.org \
--cc=david.hunter.linux@gmail.com \
--cc=kashyap.desai@broadcom.com \
--cc=khalid@kernel.org \
--cc=kubik.bartlomiej@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpi3mr-linuxdrv.pdl@broadcom.com \
--cc=sathya.prakash@broadcom.com \
--cc=skhan@linuxfoundation.org \
--cc=sreekanth.reddy@broadcom.com \
--cc=sumit.saxena@broadcom.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
all inboxes | Powered by JetHome®