From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
jejb@linux.ibm.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 00/10] Fix a bunch SCSI related W=1 warnings
Date: Wed, 08 Jul 2020 03:17:08 -0400 [thread overview]
Message-ID: <yq1mu4azea8.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20200708065100.GK3500@dell> (Lee Jones's message of "Wed, 8 Jul 2020 07:51:00 +0100")
Lee,
> Out of interest, do you know of any other efforts to fix W=1 warnings
> in SCSI?
I am not.
I try to encourage that all new patches get compiled with C=1/W=1. If I
could, I would strictly enforce this. However, there is just too much
vintage code around at this point. And even some of the most actively
developed "contemporary" drivers suffer from a large amount of sparse
warnings. Would love to see things cleaned up.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-07-08 7:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 14:00 [PATCH 00/10] Fix a bunch SCSI related W=1 warnings Lee Jones
2020-07-07 14:00 ` [PATCH 01/10] scsi: megaraid: megaraid_mm: Strip excess function param description Lee Jones
2020-07-07 14:00 ` [PATCH 02/10] scsi: megaraid: megaraid_mbox: Fix some kerneldoc bitrot Lee Jones
2020-07-07 14:00 ` [PATCH 03/10] scsi: fdomain: Mark 'fdomain_pm_ops' as __maybe_unused Lee Jones
2020-07-07 14:00 ` [PATCH 04/10] scsi: megaraid: megaraid_sas_fusion: Fix-up a whole myriad of kerneldoc misdemeanours Lee Jones
2020-07-07 14:00 ` [PATCH 05/10] scsi: megaraid: megaraid_sas_base: Provide prototypes for non-static functions Lee Jones
2020-07-07 14:00 ` [PATCH 06/10] scsi: aha152x: Remove unused variable 'ret' Lee Jones
2020-07-07 14:00 ` [PATCH 07/10] scsi: pcmcia: nsp_cs: Use new __printf() format notation Lee Jones
2020-07-07 14:00 ` [PATCH 08/10] scsi: pcmcia: nsp_cs: Remove unused variable 'dummy' Lee Jones
2020-07-07 14:00 ` [PATCH 09/10] scsi: libfc: fc_disc: Fix-up some incorrectly referenced function parameters Lee Jones
2020-07-08 6:30 ` Hannes Reinecke
2020-07-08 7:34 ` Johannes Thumshirn
2020-07-08 7:46 ` Lee Jones
2020-07-07 14:00 ` [PATCH 10/10] scsi: megaraid: megaraid_sas: Convert forward-declarations to prototypes Lee Jones
2020-07-08 0:53 ` [PATCH 00/10] Fix a bunch SCSI related W=1 warnings Damien Le Moal
2020-07-08 6:51 ` Lee Jones
2020-07-08 7:35 ` Damien Le Moal
2020-07-08 7:42 ` Lee Jones
2020-07-08 6:06 ` Martin K. Petersen
2020-07-08 6:51 ` Lee Jones
2020-07-08 7:17 ` Martin K. Petersen [this message]
2020-07-08 7:28 ` Lee Jones
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=yq1mu4azea8.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=jejb@linux.ibm.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.