From: Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org,
ryusuke-sG5X7nlA6pw@public.gmane.org,
Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
Subject: [PATCH 0/2] nilfs2: eliminate sparse warnings
Date: Fri, 8 Oct 2010 22:37:26 +0900 [thread overview]
Message-ID: <1286545048-21582-1-git-send-email-jir@unicus.jp> (raw)
Hi, these are trivial fixup to eliminate sparse warnings when
compiling with C=1.
First patch changes a variable and a function used only in a file static.
Second patch adds sparse annotations to stop warning for imbalance context
for lock variable.
fs/nilfs2/dat.c | 3 ++-
fs/nilfs2/segment.c | 11 +++++++++++
fs/nilfs2/super.c | 2 +-
3 files changed, 14 insertions(+), 2 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2010-10-08 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 13:37 Jiro SEKIBA [this message]
[not found] ` <1286545048-21582-1-git-send-email-jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
2010-10-08 13:37 ` [PATCH 1/2] nilfs2: eliminate sparse warnings - "symbol not declared" Jiro SEKIBA
[not found] ` <1286545048-21582-2-git-send-email-jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
2010-10-12 5:03 ` Ryusuke Konishi
2010-10-08 13:37 ` [PATCH 2/2] nilfs2: eliminate sparse warning - "context imbalance" Jiro SEKIBA
[not found] ` <1286545048-21582-3-git-send-email-jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
2010-10-12 5:15 ` Ryusuke Konishi
[not found] ` <20101012.141544.180421617.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-10-13 3:18 ` Jiro SEKIBA
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=1286545048-21582-1-git-send-email-jir@unicus.jp \
--to=jir-hfpbi5wx9j54eiagz67ipq@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ryusuke-sG5X7nlA6pw@public.gmane.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