From: Gal Pressman <galpress@amazon.com>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@ziepe.ca>
Cc: <linux-rdma@vger.kernel.org>, Gal Pressman <galpress@amazon.com>,
"Daniel Kranzdorf" <dkkranzd@amazon.com>,
Firas JahJah <firasj@amazon.com>
Subject: [PATCH for-next 1/4] RDMA/efa: Fix incorrect error print
Date: Tue, 10 Sep 2019 14:42:58 +0100 [thread overview]
Message-ID: <20190910134301.4194-2-galpress@amazon.com> (raw)
In-Reply-To: <20190910134301.4194-1-galpress@amazon.com>
The error print should indicate that it failed to get the queue
attributes, not network attributes.
Reviewed-by: Daniel Kranzdorf <dkkranzd@amazon.com>
Reviewed-by: Firas JahJah <firasj@amazon.com>
Signed-off-by: Gal Pressman <galpress@amazon.com>
---
drivers/infiniband/hw/efa/efa_com_cmd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/infiniband/hw/efa/efa_com_cmd.c b/drivers/infiniband/hw/efa/efa_com_cmd.c
index 501dce89f275..c079f1332082 100644
--- a/drivers/infiniband/hw/efa/efa_com_cmd.c
+++ b/drivers/infiniband/hw/efa/efa_com_cmd.c
@@ -481,7 +481,7 @@ int efa_com_get_device_attr(struct efa_com_dev *edev,
EFA_ADMIN_QUEUE_ATTR);
if (err) {
ibdev_err_ratelimited(edev->efa_dev,
- "Failed to get network attributes %d\n",
+ "Failed to get queue attributes %d\n",
err);
return err;
}
--
2.23.0
next prev parent reply other threads:[~2019-09-10 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 13:42 [PATCH for-next 0/4] EFA RDMA read support Gal Pressman
2019-09-10 13:42 ` Gal Pressman [this message]
2019-09-16 17:37 ` [PATCH for-next 1/4] RDMA/efa: Fix incorrect error print Jason Gunthorpe
2019-09-10 13:42 ` [PATCH for-next 2/4] RDMA/efa: Store network attributes in device attributes Gal Pressman
2019-09-10 13:43 ` [PATCH for-next 3/4] RDMA/efa: Support remote read access in MR registration Gal Pressman
2019-09-10 13:43 ` [PATCH for-next 4/4] RDMA/efa: Expose RDMA read related attributes Gal Pressman
2019-10-20 7:03 ` [PATCH for-next 0/4] EFA RDMA read support Gal Pressman
2019-10-21 17:31 ` Jason Gunthorpe
2019-10-23 9:55 ` Gal Pressman
2019-10-23 14:35 ` Jason Gunthorpe
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=20190910134301.4194-2-galpress@amazon.com \
--to=galpress@amazon.com \
--cc=dkkranzd@amazon.com \
--cc=dledford@redhat.com \
--cc=firasj@amazon.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@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).