DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: David Marchand <david.marchand@redhat.com>,
	Olivier Matz <olivier.matz@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Fan Zhang <royzhang1980@gmail.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXT] Re: [PATCH] cryptodev: fix unduly newlines in logs
Date: Fri, 30 Sep 2022 18:47:54 +0000	[thread overview]
Message-ID: <CO6PR18MB44843111317CDA0B0D79E679D8569@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8xT7WD-zYO=JmUD3TYag=J=xPo3_bReNRRrGx3DMkZ6eA@mail.gmail.com>

> On Thu, Sep 29, 2022 at 2:05 PM Olivier Matz <olivier.matz@6wind.com> wrote:
> >
> > The CDEV_LOG_* macros already add a '\n' at the end of
> > the line. Remove it from format strings to avoid duplicated
> > newlines.
> >
> > Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
> 
> I had the exact same patch in store :-).
> We may want to backport it, but otherwise:
> Reviewed-by: David Marchand <david.marchand@redhat.com>
> 
Added fixes tags.
Fixes: 725d2a7fbf7 ("cryptodev: add APIs to assist PMD initialisation")
Fixes: e764cd72a9b ("cryptodev: update symmetric session structure")
Fixes: 1d6f89885e1 ("cryptodev: add sym session mempool create")
Fixes: 1f1e4b7cbaa ("cryptodev: use single mempool for asymmetric session")
Fixes: 757f40e28e1 ("cryptodev: modify return value for asym session create")
Fixes: cea66374dcb ("cryptodev: support asymmetric operations")
Cc: stable@dpdk.org

Acked-by: Akhil Goyal <gakhil@marvell.com>

Applied to dpdk-next-crypto

Thanks for fixes Olivier.

      reply	other threads:[~2022-09-30 18:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 12:05 Olivier Matz
2022-09-30  6:42 ` David Marchand
2022-09-30 18:47   ` Akhil Goyal [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=CO6PR18MB44843111317CDA0B0D79E679D8569@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.com \
    --cc=royzhang1980@gmail.com \
    --cc=stable@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).