From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linux-nfs@vger.kernel.org,
Anna Schumaker <anna.schumaker@netapp.com>,
Benjamin Coddington <bcodding@redhat.com>,
Christoph Hellwig <hch@lst.de>,
Colin Ian King <colin.king@canonical.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
Jeff Layton <jlayton@poochiereds.net>,
Trond Myklebust <trond.myklebust@primarydata.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 0/2] lockd: Adjustments for some function implementations
Date: Thu, 17 Aug 2017 16:32:10 +0200 [thread overview]
Message-ID: <e53b2d3a-239a-268c-5674-3c50b02c966f@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Thu, 17 Aug 2017 16:17:18 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation in reclaimer()
Adjust 61 checks for null pointers
fs/lockd/clnt4xdr.c | 12 ++++++------
fs/lockd/clntlock.c | 16 ++++++----------
fs/lockd/clntproc.c | 12 ++++++------
fs/lockd/clntxdr.c | 12 ++++++------
fs/lockd/host.c | 22 +++++++++++-----------
fs/lockd/mon.c | 16 ++++++++--------
fs/lockd/svc.c | 4 ++--
fs/lockd/svc4proc.c | 6 +++---
fs/lockd/svclock.c | 14 +++++++-------
fs/lockd/svcproc.c | 6 +++---
fs/lockd/svcshare.c | 2 +-
fs/lockd/svcsubs.c | 3 +--
12 files changed, 60 insertions(+), 65 deletions(-)
--
2.14.0
next reply other threads:[~2017-08-17 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 14:32 SF Markus Elfring [this message]
2017-08-17 14:33 ` [PATCH 1/2] lockd: Delete an error message for a failed memory allocation in reclaimer() SF Markus Elfring
2017-08-17 14:34 ` [PATCH 2/2] lockd: Adjust 61 checks for null pointers SF Markus Elfring
2017-08-18 15:53 ` Trond Myklebust
2017-08-18 16:04 ` Jeff Layton
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=e53b2d3a-239a-268c-5674-3c50b02c966f@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=anna.schumaker@netapp.com \
--cc=bcodding@redhat.com \
--cc=bfields@fieldses.org \
--cc=colin.king@canonical.com \
--cc=hch@lst.de \
--cc=jlayton@poochiereds.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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;
as well as URLs for NNTP newsgroup(s).