From: Jules Irenge <jbi.octave@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: boqun.feng@gmail.com
Subject: [PATCH 0/5] lock warnings cleanup
Date: Fri, 3 Apr 2020 17:05:00 +0100 [thread overview]
Message-ID: <20200403160505.2832-1-jbi.octave@gmail.com> (raw)
In-Reply-To: <0/5>
This patch series adds missing annotations to various functions,
that register warnings of context imbalance when built with Sparse tool.
The adds fix the warnings, improve on readability of the code
and give better insight or directive on what the functions are actually doing.
Jules Irenge (5):
ipc/msg: Add missing annotation for freeque()
video: Add missing annotation for cyber2000fb_enable_ddc() and
cyber2000fb_disable_ddc()
ocfs2: Add missing annotation for dlm_empty_lockres()
libata: Add missing annotation for ata_scsi_rbuf_get() and
ata_scsi_rbuf_fill()
ipmi: Add missing annotation for ipmi_ssif_lock_cond() and
ipmi_ssif_unlock_cond()
drivers/ata/libata-scsi.c | 2 ++
drivers/char/ipmi/ipmi_ssif.c | 2 ++
drivers/video/fbdev/cyber2000fb.c | 2 ++
fs/ocfs2/dlm/dlmmaster.c | 1 +
ipc/msg.c | 2 ++
5 files changed, 9 insertions(+)
--
2.24.1
next parent reply other threads:[~2020-04-03 16:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0/5>
2020-04-03 16:05 ` Jules Irenge [this message]
2020-04-03 16:05 ` [PATCH 1/5] ipc/msg: Add missing annotation for freeque() Jules Irenge
2020-04-03 16:05 ` [PATCH 2/5] video: Add missing annotation for cyber2000fb_enable_ddc() and cyber2000fb_disable_ddc() Jules Irenge
2020-04-07 19:48 ` Sam Ravnborg
2020-04-03 16:05 ` [PATCH 3/5] ocfs2: Add missing annotation for dlm_empty_lockres() Jules Irenge
2020-04-03 23:45 ` Joseph Qi
2020-04-16 3:02 ` Andrew Morton
2020-04-03 16:05 ` [PATCH 4/5] libata: Add missing annotation for ata_scsi_rbuf_get() and ata_scsi_rbuf_fill() Jules Irenge
2020-04-03 16:05 ` [PATCH 5/5] ipmi: Add missing annotation for ipmi_ssif_lock_cond() and ipmi_ssif_unlock_cond() Jules Irenge
2020-04-03 18:35 ` Corey Minyard
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=20200403160505.2832-1-jbi.octave@gmail.com \
--to=jbi.octave@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox