From: Davidlohr Bueso <dave@stgolabs.net>
To: linux-cxl@vger.kernel.org
Cc: dan.j.williams@intel.com, ben.widawsky@intel.com,
ira.weiny@intel.com, vishal.l.verma@intel.com,
alison.schofield@intel.com, a.manzanares@samsung.com,
dave@stgolabs.net
Subject: [PATCH 1/4] cxl/mbox: Drop mbox_mutex comment
Date: Sun, 3 Apr 2022 19:12:13 -0700 [thread overview]
Message-ID: <20220404021216.66841-2-dave@stgolabs.net> (raw)
In-Reply-To: <20220404021216.66841-1-dave@stgolabs.net>
... we have lockdep for this.
Reviewed by: Adam Manzanares <a.manzanares@samsung.com>
Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
---
drivers/cxl/core/mbox.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cxl/core/mbox.c b/drivers/cxl/core/mbox.c
index be61a0d8016b..a586c0fa9555 100644
--- a/drivers/cxl/core/mbox.c
+++ b/drivers/cxl/core/mbox.c
@@ -136,7 +136,7 @@ static struct cxl_mem_command *cxl_mem_find_command(u16 opcode)
* @out: Caller allocated buffer for the output.
* @out_size: Expected size of output.
*
- * Context: Any context. Will acquire and release mbox_mutex.
+ * Context: Any context.
* Return:
* * %>=0 - Number of bytes returned in @out.
* * %-E2BIG - Payload is too large for hardware.
--
2.26.2
next prev parent reply other threads:[~2022-04-04 2:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 2:12 [PATCH v2 0/4] cxl/mbox: Robustify handling of mbox_cmd.return_code Davidlohr Bueso
2022-04-04 2:12 ` Davidlohr Bueso [this message]
2022-04-04 2:12 ` [PATCH 2/4] cxl/pci: Use CXL_MBOX_SUCCESS to check against mbox_cmd return code Davidlohr Bueso
2022-04-04 2:12 ` [PATCH 3/4] cxl/mbox: Improve handling of mbox_cmd hw return codes Davidlohr Bueso
2022-04-04 2:12 ` [PATCH 4/4] cxl/mbox: Use new return_code handling Davidlohr Bueso
2022-04-04 3:39 ` [PATCH v2 0/4] cxl/mbox: Robustify handling of mbox_cmd.return_code Dan Williams
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=20220404021216.66841-2-dave@stgolabs.net \
--to=dave@stgolabs.net \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=ben.widawsky@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--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