From: kbuild test robot <lkp@intel.com>
To: Trond Myklebust <trond.myklebust@hammerspace.com>
Cc: kbuild-all@01.org, linux-nfs@vger.kernel.org
Subject: [nfs:testing 18/19] fs/nfs/dir.c:196:51-52: Unneeded semicolon
Date: Mon, 8 Jul 2019 00:46:34 +0800 [thread overview]
Message-ID: <201907080032.BxKfahLm%lkp@intel.com> (raw)
tree: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git testing
head: c433a7975cfc839906aaa891f68d86ca228f7e43
commit: 36cdd6c6a8416b6a455ddc0b104eaf94eb37d39e [18/19] NFS: Ensure cached readdir info is NUL terminated
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
coccinelle warnings: (new ones prefixed by >>)
>> fs/nfs/dir.c:196:51-52: Unneeded semicolon
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2019-07-07 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 16:46 kbuild test robot [this message]
2019-07-07 16:46 ` [PATCH] NFS: fix semicolon.cocci warnings kbuild test robot
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=201907080032.BxKfahLm%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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