From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Nilesh Javali <njavali@marvell.com>,
Manish Rangankar <mrangankar@marvell.com>,
GR-QLogic-Storage-Upstream@marvell.com (supporter:QLOGIC QL41xxx
ISCSI DRIVER), "James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org (open list:QLOGIC QL41xxx ISCSI
DRIVER)
Subject: [PATCH v2 0/2] scsi: qedi: Couple of warning fixes
Date: Fri, 26 Nov 2021 12:17:06 -0800 [thread overview]
Message-ID: <20211126201708.27140-1-f.fainelli@gmail.com> (raw)
These warnings started to show up after enabling PCI on BMIPS (32-bit
MIPS architecture) and were reported by the kbuild robot.
I don't know whether they are technically correct, in particular the
unused 'page' variable might be unveiling a genuine bug whereby it
should have been used. Please review.
Changes in v2:
- added Acked-by to patch #1
- changed SYSFS_FLAG_FW_SEL_BOOT to contain the typecasting and not
change the way it is formatted before sysfs printing
Florian Fainelli (2):
scsi: qedi: Remove set but unused 'page' variable
scsi: qedi: Fix SYSFS_FLAG_FW_SEL_BOOT formatting
drivers/scsi/qedi/qedi.h | 2 +-
drivers/scsi/qedi/qedi_main.c | 3 ---
2 files changed, 1 insertion(+), 4 deletions(-)
--
2.25.1
next reply other threads:[~2021-11-27 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 20:17 Florian Fainelli [this message]
2021-11-26 20:17 ` [PATCH v2 1/2] scsi: qedi: Remove set but unused 'page' variable Florian Fainelli
2021-11-30 4:00 ` Martin K. Petersen
2021-11-26 20:17 ` [PATCH v2 2/2] scsi: qedi: Fix SYSFS_FLAG_FW_SEL_BOOT formatting Florian Fainelli
2021-11-29 7:29 ` [EXT] " Manish Rangankar
2021-11-30 3:59 ` Martin K. Petersen
2021-11-30 4:09 ` Florian Fainelli
2021-11-30 4:25 ` Martin K. Petersen
2021-12-03 3:03 ` [PATCH v2 0/2] scsi: qedi: Couple of warning fixes Martin K. Petersen
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=20211126201708.27140-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mrangankar@marvell.com \
--cc=njavali@marvell.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