From: Bruce Richardson <bruce.richardson@intel.com>
To: Arnon Warshavsky <arnon@qwilt.com>
Cc: thomas@monjalon.net, anatoly.burakov@intel.com,
wenzhuo.lu@intel.com, declan.doherty@intel.com,
jerin.jacob@caviumnetworks.com, ferruh.yigit@intel.com,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 01/13] crypto: replace rte_panic instances in crypto driver
Date: Wed, 4 Apr 2018 14:10:31 +0100 [thread overview]
Message-ID: <20180404131030.GA30584@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <1522841257-11826-2-git-send-email-arnon@qwilt.com>
On Wed, Apr 04, 2018 at 02:27:25PM +0300, Arnon Warshavsky wrote:
> Signed-off-by: Arnon Warshavsky <arnon@qwilt.com>
> ---
> drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 8 +++++---
> drivers/crypto/dpaa_sec/dpaa_sec.c | 8 +++++---
> 2 files changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
> index 784b96d..37a5727 100644
> --- a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
> +++ b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
> @@ -2861,9 +2861,11 @@ struct rte_security_ops dpaa2_sec_security_ops = {
> RTE_CACHE_LINE_SIZE,
> rte_socket_id());
>
> - if (cryptodev->data->dev_private == NULL)
> - rte_panic("Cannot allocate memzone for private "
> - "device data");
> + if (cryptodev->data->dev_private == NULL) {
> + RTE_LOG(ERR, PMD, "%s() Cannot allocate memzone for "
> + "private device data", __func__);
> + return -1;
> + }
> }
This is the right change to make, but can you please avoid wrapping literal
strings across lines. It means that the error message cannot be grepped.
Just put the __func__ on the second line.
Checkpatch and similar tools should ignore long lines if the long line is
simply caused by a literal string.
/Bruce
next prev parent reply other threads:[~2018-04-04 13:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 11:27 [dpdk-dev] eal: replace calls to rte_panic and refrain from new instances Arnon Warshavsky
2018-04-04 11:27 ` [dpdk-dev] [PATCH 01/13] crypto: replace rte_panic instances in crypto driver Arnon Warshavsky
2018-04-04 13:10 ` Bruce Richardson [this message]
2018-04-04 20:43 ` Arnon Warshavsky
2018-04-04 11:27 ` [dpdk-dev] [PATCH 02/13] bond: replace rte_panic instances in bonding driver Arnon Warshavsky
2018-04-04 11:27 ` [dpdk-dev] [PATCH 03/13] e1000: replace rte_panic instances in e1000 driver Arnon Warshavsky
2018-04-04 11:27 ` [dpdk-dev] [PATCH 04/13] ixgbe: replace rte_panic instances in ixgbe driver Arnon Warshavsky
2018-04-04 11:27 ` [dpdk-dev] [PATCH 05/13] eal: replace rte_panic instances in eventdev Arnon Warshavsky
2018-04-04 11:27 ` [dpdk-dev] [PATCH 06/13] kni: replace rte_panic instances in kni Arnon Warshavsky
2018-04-04 11:27 ` [dpdk-dev] [PATCH 07/13] eal: replace rte_panic instances in rte_malloc Arnon Warshavsky
2018-04-04 11:56 ` Burakov, Anatoly
2018-04-04 11:27 ` [dpdk-dev] [PATCH 08/13] eal: replace rte_panic instances in hugepage_info Arnon Warshavsky
2018-04-04 11:57 ` Burakov, Anatoly
2018-04-04 11:27 ` [dpdk-dev] [PATCH 09/13] eal: replace rte_panic instances in common_memzone Arnon Warshavsky
2018-04-04 12:09 ` Burakov, Anatoly
2018-04-04 12:34 ` Thomas Monjalon
2018-04-04 20:44 ` Arnon Warshavsky
2018-04-04 11:27 ` [dpdk-dev] [PATCH 10/13] eal: replace rte_panic instances in interrupts thread Arnon Warshavsky
2018-04-04 11:27 ` [dpdk-dev] [PATCH 11/13] eal: replace rte_panic instances in ethdev Arnon Warshavsky
2018-04-04 11:27 ` [dpdk-dev] [PATCH 12/13] eal: replace rte_panic instances in init sequence Arnon Warshavsky
2018-04-04 11:27 ` [dpdk-dev] [PATCH 13/13] devtools: prevent new instances of rte_panic and rte_exit Arnon Warshavsky
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=20180404131030.GA30584@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=arnon@qwilt.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=thomas@monjalon.net \
--cc=wenzhuo.lu@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;
as well as URLs for NNTP newsgroup(s).