From: SF Markus Elfring <elfring@users.sourceforge.net>
To: ceph-devel@vger.kernel.org, Ilya Dryomov <idryomov@gmail.com>,
Sage Weil <sage@redhat.com>, "Yan, Zheng" <zyan@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 0/3] Ceph: Adjustments for some function implementations
Date: Sun, 20 Aug 2017 18:37:49 +0000 [thread overview]
Message-ID: <b05df66b-b8a7-ac63-989d-091efecf2ab8@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Sun, 20 Aug 2017 20:32:10 +0200
Three update suggestions were taken into account
from static source code analysis.
Markus Elfring (3):
Delete an error message for a failed memory allocation in __get_or_create_frag()
Delete an unnecessary return statement in update_dentry_lease()
Adjust 36 checks for null pointers
fs/ceph/addr.c | 2 +-
fs/ceph/cache.c | 2 +-
fs/ceph/caps.c | 4 ++--
fs/ceph/debugfs.c | 2 +-
fs/ceph/file.c | 2 +-
fs/ceph/inode.c | 14 +++++---------
fs/ceph/mds_client.c | 22 +++++++++++-----------
fs/ceph/mdsmap.c | 6 +++---
fs/ceph/super.c | 18 +++++++++---------
fs/ceph/xattr.c | 8 ++++----
10 files changed, 38 insertions(+), 42 deletions(-)
--
2.14.0
next reply other threads:[~2017-08-20 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 18:37 SF Markus Elfring [this message]
2017-08-20 18:38 ` [PATCH 1/3] ceph: Delete an error message for a failed memory allocation in __get_or_create_frag() SF Markus Elfring
2017-08-20 18:39 ` [PATCH 2/3] ceph: Delete an unnecessary return statement in update_dentry_lease() SF Markus Elfring
2017-08-20 18:40 ` [PATCH 3/3] ceph: Adjust 36 checks for null pointers SF Markus Elfring
2017-08-21 1:46 ` [PATCH 0/3] Ceph: Adjustments for some function implementations Yan, Zheng
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=b05df66b-b8a7-ac63-989d-091efecf2ab8@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@redhat.com \
--cc=zyan@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox