From: Abinash Singh <abinashsinghlalotra@gmail.com>
To: abinashsinghlalotra@gmail.com
Cc: James.Bottomley@HansenPartnership.com, bvanassche@acm.org,
dlemoal@kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
kernel test robot <lkp@intel.com>
Subject: [PATCH v6 0/2] scsi: sd: Fix build warning in sd_revalidate_disk()
Date: Sat, 9 Aug 2025 15:05:05 +0530 [thread overview]
Message-ID: <20250809093507.372430-1-abinashsinghlalotra@gmail.com> (raw)
This v6 series follows up on v5 of the "scsi: sd: Fix build warning in
sd_revalidate_disk()" patches.
In v5, the change was split into two
patches: the first patch refactors sd_revalidate_disk() to return void,
and the second patch addresses excessive stack usage by allocating
certain structures dynamically.
Apologies for the oversight in v5 — although I built and tested the
kernel locally with the correct changes, I mistakenly sent an older
version of patch 2/2 that still had `size(*lim)` instead of
`sizeof(*lim)`. This caused a build error reported by the kernel test
robot when building with clang.
Changes in v6:
- Replace `size(*lim)` with `sizeof(*lim)` in patch 2/2
Now there are no build errors.
I am very sorry for that .
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202508091640.gvFPjI6O-lkp@intel.com/
Abinash Singh (2):
scsi: sd: make sd_revalidate_disk() return void
scsi: sd: Fix build warning in sd_revalidate_disk()
drivers/scsi/sd.c | 54 +++++++++++++++++++++++++++--------------------
1 file changed, 31 insertions(+), 23 deletions(-)
--
2.50.1
next reply other threads:[~2025-08-09 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 9:35 Abinash Singh [this message]
2025-08-09 9:35 ` [PATCH v6 1/2] scsi: sd: make sd_revalidate_disk() return void Abinash Singh
2025-08-09 9:35 ` [PATCH v6 2/2] scsi: sd: Fix build warning in sd_revalidate_disk() Abinash Singh
2025-08-11 0:39 ` [PATCH v6 0/2] " Damien Le Moal
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=20250809093507.372430-1-abinashsinghlalotra@gmail.com \
--to=abinashsinghlalotra@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkp@intel.com \
--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
all inboxes | Powered by JetHome®