From: kernel test robot <lkp@intel.com>
To: Ingo Rohloff <ingo.rohloff@lauterbach.com>, balbi@kernel.org
Cc: kbuild-all@lists.01.org, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org,
Ingo Rohloff <ingo.rohloff@lauterbach.com>
Subject: [RFC PATCH] usb: gadget: ffs: async_bulkurb_active_lock can be static
Date: Sun, 15 Nov 2020 18:59:12 +0800 [thread overview]
Message-ID: <20201115105912.GA59036@a7d5672ee687> (raw)
In-Reply-To: <20201111170718.3381-2-ingo.rohloff@lauterbach.com>
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
f_fs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/function/f_fs.c b/drivers/usb/gadget/function/f_fs.c
index 194d45d940313..b59e144ad7e0e 100644
--- a/drivers/usb/gadget/function/f_fs.c
+++ b/drivers/usb/gadget/function/f_fs.c
@@ -237,7 +237,7 @@ enum {
FFS_BULKURB_STATE_PENDING = 1,
FFS_BULKURB_STATE_ACTIVE = 2
};
-DEFINE_SPINLOCK(async_bulkurb_active_lock);
+static DEFINE_SPINLOCK(async_bulkurb_active_lock);
struct async_bulkurb {
struct ffs_epfile *epfile;
struct list_head urblist;
next prev parent reply other threads:[~2020-11-15 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 17:07 [PATCH 0/2] usb: gadget: User space URBs for FunctionFS Ingo Rohloff
2020-11-11 17:07 ` [PATCH 1/2] usb: gadget: ffs: Implement user URBs for USB bulk endpoints Ingo Rohloff
2020-11-15 10:59 ` kernel test robot
2020-11-15 10:59 ` kernel test robot [this message]
2020-11-11 17:07 ` [PATCH 2/2] usb: gadget: ffs: tools: test applications for user URBs Ingo Rohloff
2020-11-11 18:40 ` [PATCH 0/2] usb: gadget: User space URBs for FunctionFS Greg KH
2020-11-12 17:05 ` Ingo Rohloff
2020-11-13 14:20 ` Greg KH
2020-11-13 15:20 ` Ingo Rohloff
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=20201115105912.GA59036@a7d5672ee687 \
--to=lkp@intel.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=ingo.rohloff@lauterbach.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-usb@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).