From: Thorsten Blum <thorsten.blum@linux.dev>
To: David Laight <david.laight.linux@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: pmcraid: Replace cpu_to_be64 + le64_to_cpu with swab64
Date: Wed, 10 Dec 2025 23:45:02 +0100 [thread overview]
Message-ID: <2A50F908-C2F2-437F-A817-889C507FBF13@linux.dev> (raw)
In-Reply-To: <20251210222100.66ac5c88@pumpkin>
On 10. Dec 2025, at 23:21, David Laight wrote:
>
> [...]
>
> You'd need to run sparse.
I compiled it with C=1 and there are other, unrelated sparse warnings:
CC [M] drivers/scsi/pmcraid.o
CHECK drivers/scsi/pmcraid.c
drivers/scsi/pmcraid.c:73:1: error: bad constant expression
drivers/scsi/pmcraid.c:74:1: error: bad constant expression
drivers/scsi/pmcraid.c:75:1: error: bad constant expression
drivers/scsi/pmcraid.c:76:1: error: bad constant expression
drivers/scsi/pmcraid.c:78:1: error: bad constant expression
drivers/scsi/pmcraid.c:79:1: error: bad constant expression
drivers/scsi/pmcraid.c:84:1: error: bad constant expression
drivers/scsi/pmcraid.c:85:1: error: bad constant expression
drivers/scsi/pmcraid.c:89:1: error: bad constant expression
drivers/scsi/pmcraid.c:90:1: error: bad constant expression
Compiling with V=1 also confirms that sparse is running:
# CHECK drivers/scsi/pmcraid.c
sparse -D__linux__ ... -D__KBUILD_MODNAME=pmcraid drivers/scsi/pmcraid.c
prev parent reply other threads:[~2025-12-10 22:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 14:33 [PATCH] scsi: pmcraid: Replace cpu_to_be64 + le64_to_cpu with swab64 Thorsten Blum
2025-12-10 15:13 ` Christoph Hellwig
2025-12-10 15:39 ` Thorsten Blum
2025-12-10 22:21 ` David Laight
2025-12-10 22:45 ` Thorsten Blum [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=2A50F908-C2F2-437F-A817-889C507FBF13@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=James.Bottomley@hansenpartnership.com \
--cc=david.laight.linux@gmail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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