DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 1/5] qat: remove redundant C register keyword
Date: Tue, 31 Jul 2018 09:30:55 -0700	[thread overview]
Message-ID: <20180731163059.27085-2-stephen@networkplumber.org> (raw)
In-Reply-To: <20180731163059.27085-1-stephen@networkplumber.org>

Modern C compilers ignore the register keyword and do automatic
register assignment.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 drivers/common/qat/qat_qp.c  | 10 +++++-----
 drivers/crypto/qat/qat_sym.c |  2 +-
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/drivers/common/qat/qat_qp.c b/drivers/common/qat/qat_qp.c
index 7ca7a45ebfe0..21891ec1955d 100644
--- a/drivers/common/qat/qat_qp.c
+++ b/drivers/common/qat/qat_qp.c
@@ -530,13 +530,13 @@ void rxq_free_desc(struct qat_qp *qp, struct qat_queue *q)
 uint16_t
 qat_enqueue_op_burst(void *qp, void **ops, uint16_t nb_ops)
 {
-	register struct qat_queue *queue;
+	struct qat_queue *queue;
 	struct qat_qp *tmp_qp = (struct qat_qp *)qp;
-	register uint32_t nb_ops_sent = 0;
-	register int ret;
+	uint32_t nb_ops_sent = 0;
+	int ret;
 	uint16_t nb_ops_possible = nb_ops;
-	register uint8_t *base_addr;
-	register uint32_t tail;
+	uint8_t *base_addr;
+	uint32_t tail;
 	int overflow;
 
 	if (unlikely(nb_ops == 0))
diff --git a/drivers/crypto/qat/qat_sym.c b/drivers/crypto/qat/qat_sym.c
index 8273968f3aa7..dc77ca870fc9 100644
--- a/drivers/crypto/qat/qat_sym.c
+++ b/drivers/crypto/qat/qat_sym.c
@@ -150,7 +150,7 @@ qat_sym_build_request(void *in_op, uint8_t *out_msg,
 	struct qat_sym_session *ctx;
 	struct icp_qat_fw_la_cipher_req_params *cipher_param;
 	struct icp_qat_fw_la_auth_req_params *auth_param;
-	register struct icp_qat_fw_la_bulk_req *qat_req;
+	struct icp_qat_fw_la_bulk_req *qat_req;
 	uint8_t do_auth = 0, do_cipher = 0, do_aead = 0;
 	uint32_t cipher_len = 0, cipher_ofs = 0;
 	uint32_t auth_len = 0, auth_ofs = 0;
-- 
2.18.0

  reply	other threads:[~2018-07-31 16:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 16:30 [dpdk-dev] [PATCH 0/5] remove usage of register keyword in C Stephen Hemminger
2018-07-31 16:30 ` Stephen Hemminger [this message]
2018-09-05 10:23   ` [dpdk-dev] [PATCH 1/5] qat: remove redundant C register keyword Jozwiak, TomaszX
2018-07-31 16:30 ` [dpdk-dev] [PATCH 2/5] qede: remove register from declaraitons Stephen Hemminger
2018-07-31 16:30 ` [dpdk-dev] [PATCH 3/5] ark: remove register keyword Stephen Hemminger
2018-07-31 16:30 ` [dpdk-dev] [PATCH 4/5] mlx5: no need for " Stephen Hemminger
2018-07-31 16:30 ` [dpdk-dev] [PATCH 5/5] mlx4: remove redunant " Stephen Hemminger
2018-07-31 16:48 ` [dpdk-dev] [PATCH 0/5] remove usage of register keyword in C Adrien Mazarguil
2018-07-31 18:07   ` Stephen Hemminger
2018-08-01 18:03     ` Yongseok Koh
2018-08-01 21:03       ` Stephen Hemminger
2018-08-23 13:07         ` Ferruh Yigit
2018-10-09  9:19           ` Ferruh Yigit
2019-01-31  8:02             ` Tom Barbette
2019-01-31  9:11               ` Bruce Richardson
2019-01-31  9:39                 ` Tom Barbette
2019-01-31 17:34                 ` Wiles, Keith
2018-08-01 10:18 ` Matan Azrad

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=20180731163059.27085-2-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.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).