From: Luis de Bethencourt <luisbg@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: clm@fb.com, jbacik@fb.com, dsterba@suse.com,
linux-btrfs@vger.kernel.org,
Luis de Bethencourt <luisbg@osg.samsung.com>
Subject: [PATCH v2 0/2] btrfs: Fix returned errno codes
Date: Thu, 24 Sep 2015 20:13:31 +0100 [thread overview]
Message-ID: <cover.1443121865.git.luisbg@osg.samsung.com> (raw)
Hi,
These two patches fix instances where -1 is used to specify a buffer
allocation fail, instead of using -ENOMEM.
Patch 1/2 is already reviewed by David Sterba.
Luis de Bethencourt (2):
btrfs: check-integrity: Fix returned errno codes
btrfs: reada: Fix returned errno code
fs/btrfs/check-integrity.c | 4 ++--
fs/btrfs/reada.c | 8 +++++---
2 files changed, 7 insertions(+), 5 deletions(-)
--
2.5.1
next reply other threads:[~2015-09-24 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 19:13 Luis de Bethencourt [this message]
2015-09-24 19:13 ` [PATCH v2 1/2] btrfs: check-integrity: Fix returned errno codes Luis de Bethencourt
2015-09-24 19:13 ` [PATCH v2 2/2] btrfs: reada: Fix returned errno code Luis de Bethencourt
2015-09-25 10:40 ` David Sterba
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=cover.1443121865.git.luisbg@osg.samsung.com \
--to=luisbg@osg.samsung.com \
--cc=clm@fb.com \
--cc=dsterba@suse.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).