From: kernel test robot <lkp@intel.com>
To: Benjamin Coddington <bcodding@redhat.com>,
trond.myklebust@hammerspace.com, anna@kernel.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2 2/2] NFSv4: Allow per-mount tuning of READDIR attrs
Date: Thu, 19 Oct 2023 23:01:27 +0800 [thread overview]
Message-ID: <202310192243.5P3bLEvI-lkp@intel.com> (raw)
In-Reply-To: <fbd3cd01c28e8c132058ae16b22eeae5ddaa8178.1697722160.git.bcodding@redhat.com>
Hi Benjamin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 401644852d0b2a278811de38081be23f74b5bb04]
url: https://github.com/intel-lab-lkp/linux/commits/Benjamin-Coddington/NFSv4-Always-ask-for-type-with-READDIR/20231019-213911
base: 401644852d0b2a278811de38081be23f74b5bb04
patch link: https://lore.kernel.org/r/fbd3cd01c28e8c132058ae16b22eeae5ddaa8178.1697722160.git.bcodding%40redhat.com
patch subject: [PATCH v2 2/2] NFSv4: Allow per-mount tuning of READDIR attrs
reproduce: (https://download.01.org/0day-ci/archive/20231019/202310192243.5P3bLEvI-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202310192243.5P3bLEvI-lkp@intel.com/
# many are suggestions rather than must-fix
WARNING:LINE_SPACING: Missing a blank line after declarations
#110: FILE: fs/nfs/sysfs.c:281:
+ struct nfs_server *server;
+ server = container_of(kobj, struct nfs_server, kobj);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-19 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 13:33 [PATCH v2 0/2] NFSv4 READDIR d_type fixup Benjamin Coddington
2023-10-19 13:34 ` [PATCH v2 1/2] NFSv4: Always ask for type with READDIR Benjamin Coddington
2023-10-19 13:34 ` [PATCH v2 2/2] NFSv4: Allow per-mount tuning of READDIR attrs Benjamin Coddington
2023-10-19 15:01 ` kernel test robot [this message]
2023-10-19 16:55 ` Jeff Layton
2023-10-19 17:31 ` Benjamin Coddington
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=202310192243.5P3bLEvI-lkp@intel.com \
--to=lkp@intel.com \
--cc=anna@kernel.org \
--cc=bcodding@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.