From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3 1/2] kernfs: use hashed mutex and spinlock in place of global ones.
Date: Tue, 18 Jan 2022 02:54:41 +0800 [thread overview]
Message-ID: <202201180137.LkPudfBC-lkp@intel.com> (raw)
In-Reply-To: <20220113104259.1584491-2-imran.f.khan@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
Hi Imran,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on a70bf4a85b43cb952bd39dd948b103b1b3eb2cf8]
url: https://github.com/0day-ci/linux/commits/Imran-Khan/kernfs-use-hashed-mutex-and-spinlock-in-place-of-global-ones/20220113-184429
base: a70bf4a85b43cb952bd39dd948b103b1b3eb2cf8
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
includecheck warnings: (new ones prefixed by >>)
>> fs/kernfs/kernfs-internal.h: linux/mutex.h is included more than once.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next prev parent reply other threads:[~2022-01-17 18:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 10:42 [PATCH v3 0/2] kernfs: use hashed mutex and spinlock in place of global ones Imran Khan
2022-01-13 10:42 ` [PATCH v3 1/2] " Imran Khan
2022-01-13 15:08 ` kernel test robot
2022-01-13 16:37 ` Tejun Heo
2022-01-17 18:54 ` kernel test robot [this message]
2022-01-13 10:42 ` [PATCH v3 2/2] kernfs: Reduce contention around global per-fs kernfs_rwsem Imran Khan
2022-01-13 10:58 ` Greg KH
2022-01-13 16:42 ` Tejun Heo
2022-01-14 17:08 ` Imran Khan
2022-01-14 17:44 ` Tejun Heo
2022-02-02 15:10 ` Imran Khan
2022-01-25 2:55 ` [kernfs] 8652224976: WARNING:at_kernel/locking/rwsem.c:#up_write kernel test robot
2022-01-25 2:55 ` kernel test robot
2022-01-13 10:57 ` [PATCH v3 0/2] kernfs: use hashed mutex and spinlock in place of global ones Greg KH
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=202201180137.LkPudfBC-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.