From: Andrew Morton <akpm@linux-foundation.org>
To: Gang He <ghe@suse.com>
Cc: mfasheh@versity.com, jlbec@evilplan.org,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [PATCH] ocfs2: fix a static checker warning
Date: Mon, 22 May 2017 14:20:55 -0700 [thread overview]
Message-ID: <20170522142055.7ebf9fae4dbce0e3ddda806a@linux-foundation.org> (raw)
In-Reply-To: <1495428877-7440-1-git-send-email-ghe@suse.com>
On Mon, 22 May 2017 12:54:37 +0800 Gang He <ghe@suse.com> wrote:
> This patch will fix a static checker warning, this warning was
> caused by commit d56a8f32e4c662509ce50a37e78fa66c777977d3. after
> apply this patch, the error return value will not be NULL(zero).
When identifying another commit, please use the form
d56a8f32e4c6 ("ocfs2: check/fix inode block for online file check")
And when fixing warnings such as this, please quote the warning in full
and identify which checker tool generated that warning.
prev parent reply other threads:[~2017-05-22 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 4:54 Gang He
2017-05-22 9:14 ` [Ocfs2-devel] " Joseph Qi
2017-05-22 21:20 ` Andrew Morton [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=20170522142055.7ebf9fae4dbce0e3ddda806a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ghe@suse.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@versity.com \
--cc=ocfs2-devel@oss.oracle.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
Powered by JetHome