From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Tomasz Duszynski <tdu@semihalf.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] crypto/mrvl: updates and bugfixes
Date: Tue, 17 Oct 2017 11:56:01 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC35328@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1508224668-30354-1-git-send-email-tdu@semihalf.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Tomasz Duszynski
> Sent: Tuesday, October 17, 2017 8:18 AM
> To: dev@dpdk.org
> Cc: Tomasz Duszynski <tdu@semihalf.com>
> Subject: [dpdk-dev] [PATCH 0/3] crypto/mrvl: updates and bugfixes
>
> This patch series brings following changes:
>
> * A few fixes related to printing debug messages
> * Extra debug message in case dma object has been already initialized
>
> Tomasz Duszynski (3):
> crypto/mrvl: fix driver name in debug log
> crypto/mrvl: use proper config option to enable debug logs
> crypto/mrvl: print message if dma mem object is already initialized
>
> drivers/crypto/mrvl/rte_mrvl_pmd.c | 12 ++++++++----
> drivers/crypto/mrvl/rte_mrvl_pmd_private.h | 8 ++++----
> 2 files changed, 12 insertions(+), 8 deletions(-)
>
> --
> 2.7.4
I modified the last patch's title, as check-git-log.sh was complaining,
so make sure to run it next time you send patches.
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2017-10-17 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 7:17 Tomasz Duszynski
2017-10-17 7:17 ` [dpdk-dev] [PATCH 1/3] crypto/mrvl: fix driver name in debug log Tomasz Duszynski
2017-10-17 7:17 ` [dpdk-dev] [PATCH 2/3] crypto/mrvl: fix enabling debug logs Tomasz Duszynski
2017-10-17 7:17 ` [dpdk-dev] [PATCH 3/3] crypto/mrvl: print message if dma mem is initialized Tomasz Duszynski
2017-10-17 11:56 ` De Lara Guarch, Pablo [this message]
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=E115CCD9D858EF4F90C690B0DCB4D8976CC35328@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=tdu@semihalf.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).