All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@inktank.com>
To: Alex Elder <elder@inktank.com>
Cc: "ceph-devel@vger.kernel.org >> ceph-devel" <ceph-devel@vger.kernel.org>
Subject: Re: Updated sparse warning message patches
Date: Mon, 25 Feb 2013 11:15:18 -0800	[thread overview]
Message-ID: <512BB846.7060107@inktank.com> (raw)
In-Reply-To: <5127A85D.1070000@inktank.com>

On 02/22/2013 09:18 AM, Alex Elder wrote:
> I'm re-posting these patches because I've updated them to be
> based on the patches I just posted ("Four miscellaneous patches").
>
> These patches are available in the branch "test/wip-4184" in
> the ceph-client git repository.  That branch is based on
> branch "test/wip-4234,5,7,8".
>
> (Here's the original description)
>
> What follows is a few series of patches that get rid of code
> issues that lead to warnings from the sparse utility.
>
> The first three patches address the warnings in the rbd, ceph
> file system, and libceph code respectively.  After that, one
> warning remains in libceph, and that is addressed by a series
> of five patches which both address the underlying problem and
> reorganized and clean up the surrounding code.  The last two
> are meant to be combined into one before commit; they've been
> posted as two separate patches to make them easier to review.
>
> 					-Alex
>
> [PATCH, v2] rbd: eliminate sparse warnings
> [PATCH, v2] ceph: eliminate sparse warnings in fs code
> [PATCH, v2] libceph: eliminate sparse warnings
> [PATCH 1/5, v2] libceph: encapsulate connection backoff
> [PATCH 2/5, v2] libceph: separate non-locked fault handling
> [PATCH 3/5, v2] libceph: use a flag to indicate a fault has occurred
> [PATCH 4/5, v2] libceph: use a do..while loop in con_work()
> [PATCH 5/5, v2] libceph: indent properly

These all look good too.
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>


      parent reply	other threads:[~2013-02-25 19:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-22 17:18 Updated sparse warning message patches Alex Elder
2013-02-22 17:21 ` [PATCH, v2] rbd: eliminate sparse warnings Alex Elder
2013-02-22 17:21 ` [PATCH, v2] ceph: eliminate sparse warnings in fs code Alex Elder
2013-02-22 17:21 ` [PATCH, v2] libceph: eliminate sparse warnings Alex Elder
2013-02-22 17:21 ` [PATCH 0/5, v2] libceph clean up con_work() Alex Elder
2013-02-22 17:23   ` [PATCH 1/5] libceph: encapsulate connection backoff Alex Elder
2013-02-22 17:23   ` [PATCH 2/5] libceph: separate non-locked fault handling Alex Elder
2013-02-22 17:26   ` Alex Elder
2013-02-22 17:32     ` Alex Elder
2013-02-22 17:26   ` [PATCH 3/5, v2] libceph: use a flag to indicate a fault has occurred Alex Elder
2013-02-22 17:30   ` [PATCH 4/5, v2] libceph: use a do..while loop in con_work() Alex Elder
2013-02-22 17:30   ` [PATCH 5/5, v2] libceph: indent properly Alex Elder
2013-02-25 19:15 ` Josh Durgin [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=512BB846.7060107@inktank.com \
    --to=josh.durgin@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=elder@inktank.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 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.