From: David Sterba <dsterba@suse.cz>
To: Zach Brown <zab@zabbo.net>
Cc: linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.cz>
Subject: Re: [PATCH 0/4] some btrfs-progs coverity fixes
Date: Thu, 16 Oct 2014 13:46:12 +0200 [thread overview]
Message-ID: <20141016114612.GD22943@twin.jikos.cz> (raw)
In-Reply-To: <1413414861-28097-1-git-send-email-zab@zabbo.net>
On Wed, Oct 15, 2014 at 04:14:17PM -0700, Zach Brown wrote:
> Here's another set of coverity fixes for btrfs-progs against David's
> integration-20141007 branch.
Thanks, I've fished 2 patches for 3.17, the rest is queued.
> I got tired of adding error checking after a few so I moved on to the
> other warnings. Maybe we should subscribe linux-btrfs to the reports
> that coverity can send out?
I'm not sure if this is allowed by the coverity service and I was not
able to any info about that.
next prev parent reply other threads:[~2014-10-16 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 23:14 [PATCH 0/4] some btrfs-progs coverity fixes Zach Brown
2014-10-15 23:14 ` [PATCH 1/4] btrfs-progs: check sscanf return code Zach Brown
2014-10-15 23:14 ` [PATCH 2/4] btrfs-progs: check read extent errors when mapping Zach Brown
2014-10-15 23:14 ` [PATCH 3/4] btrfs-progs: fix show super unknown flag output Zach Brown
2014-10-15 23:14 ` [PATCH 4/4] btrfs-progs: fix csum root copy-n-paste error Zach Brown
2014-10-16 10:55 ` David Sterba
2014-10-16 11:46 ` David Sterba [this message]
2014-10-16 13:33 ` [PATCH 0/4] some btrfs-progs coverity fixes Eric Sandeen
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=20141016114612.GD22943@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=zab@zabbo.net \
/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).