From: Alison Schofield <alison.schofield@intel.com>
To: 13145886936@163.com
Cc: dan.j.williams@intel.com, vishal.l.verma@intel.com,
dave.jiang@intel.com, ira.weiny@intel.com,
nvdimm@lists.linux.dev, linux-kernel@vger.kernel.org,
gushengxian <gushengxian@yulong.com>
Subject: Re: [PATCH] tools/testing/nvdimm: Remove NULL test before vfree
Date: Fri, 25 Jun 2021 18:40:47 -0700 [thread overview]
Message-ID: <20210626014047.GA15626@alison-desk.jf.intel.com> (raw)
In-Reply-To: <20210626012655.515279-1-13145886936@163.com>
On Fri, Jun 25, 2021 at 06:26:55PM -0700, 13145886936@163.com wrote:
> From: gushengxian <gushengxian@yulong.com>
Hi,
Thanks for updating the commit message and log.
I think you need to do something about the Signed-off-by or this
will not be accepted. You can read more about the developer's
certificate of origin in here.
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
Not sure your particular case, but maybe -
If you are submitting this on behalf of Gushengxian, then you need
to add your Signed-off-by after the current one:
ie. Signed-off-by: Your Full Name <13145886936@163.com>
Or, if this is your work, then you may need to update your
.gitconfig file, like this:
[user]
name = Your Full Name
email = email@example.com
The From line of the email needs to match a Signed-off-by.
Each time you repost a patch please increment the version number.
The next posting would be [PATCH v3]
Alison
>
> This NULL test is redundant since vfree() checks for NULL.
> Reported by Coccinelle.
>
> Signed-off-by: gushengxian <gushengxian@yulong.com>
> ---
> tools/testing/nvdimm/test/nfit.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/nvdimm/test/nfit.c b/tools/testing/nvdimm/test/nfit.c
> index 54f367cbadae..cb86f0cbb11c 100644
> --- a/tools/testing/nvdimm/test/nfit.c
> +++ b/tools/testing/nvdimm/test/nfit.c
> @@ -1641,8 +1641,8 @@ static void *__test_alloc(struct nfit_test *t, size_t size, dma_addr_t *dma,
> err:
> if (*dma && size >= DIMM_SIZE)
> gen_pool_free(nfit_pool, *dma, size);
> - if (buf)
> - vfree(buf);
> +
> + vfree(buf);
> kfree(nfit_res);
> return NULL;
> }
> --
> 2.25.1
>
>
prev parent reply other threads:[~2021-06-26 1:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 1:26 13145886936
2021-06-26 1:40 ` Alison Schofield [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=20210626014047.GA15626@alison-desk.jf.intel.com \
--to=alison.schofield@intel.com \
--cc=13145886936@163.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=gushengxian@yulong.com \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.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
all inboxes | Powered by JetHome®