linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs: fix several sparse warnings
Date: Sun, 28 Sep 2014 01:52:30 -0700	[thread overview]
Message-ID: <20140928085230.GA31649@molino.home.network> (raw)
In-Reply-To: <1411894092-28784-1-git-send-email-osandov@osandov.com>

On Sun, Sep 28, 2014 at 01:48:10AM -0700, Omar Sandoval wrote:
> This patch series fixes some warnings reported by sparse when building the
> btrfs module. It fixes two classes of warnings: address space warnings and lock
> context warnings. This didn't uncover any logical errors, but it reduces the
> noise when checking the source. There are a few less straightforward sparse
> warnings still remaining.
> 
> Omar Sandoval (2):
>   btrfs: fix sparse address space warnings
>   btrfs: fix sparse lock context warnings
> 
>  fs/btrfs/ctree.c            | 3 ++-
>  fs/btrfs/extent-tree.c      | 1 +
>  fs/btrfs/extent_io.c        | 2 +-
>  fs/btrfs/free-space-cache.c | 1 +
>  fs/btrfs/ioctl.c            | 6 +++---
>  fs/btrfs/locking.c          | 1 +
>  fs/btrfs/send.c             | 8 ++++----
>  7 files changed, 13 insertions(+), 9 deletions(-)
> 

This patch series applies to 3.17-rc6.

-- 
Omar

      parent reply	other threads:[~2014-09-28  8:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-28  8:48 [PATCH 0/2] btrfs: fix several sparse warnings Omar Sandoval
2014-09-28  8:48 ` [PATCH 1/2] btrfs: fix sparse address space warnings Omar Sandoval
2014-09-28 22:26   ` Omar Sandoval
2014-09-30 19:27     ` Zach Brown
2014-09-30 20:32       ` Omar Sandoval
2014-09-29 16:07   ` David Sterba
2014-09-29 19:45     ` Omar Sandoval
2014-09-29 21:49       ` David Sterba
2014-09-28  8:48 ` [PATCH 2/2] btrfs: fix sparse lock context warnings Omar Sandoval
2014-09-29 16:10   ` David Sterba
2014-09-28  8:52 ` Omar Sandoval [this message]

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=20140928085230.GA31649@molino.home.network \
    --to=osandov@osandov.com \
    --cc=clm@fb.com \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).